i think issue 1 has been resolved by #190

(from [826bfbec043be19ece7f4a69e3a4ce1dc9e08213]) Fix alignment for New Job button [#198 state:resolved] https://github.com/dtolabs/rundeck/commit/826bfbec043b...

(from [2ef965fe3ed1b535ba7fdc656397ab0edef6d981]) Update node filter behavior [#190] https://github.com/dtolabs/rundeck/commit/2ef965fe3ed1b535ba7fdc656...

Well i say that because the default behavior (now) of dispatch is that no node filters dispatches to local server node only. You have to be explicit about .* to...

Reading your original post. I think if you can explain: "i don't think that "no filters" implies "all nodes" to everybody." why this is true, it might help shed...

You have a collection of nodes. By default, a filter is applied so a limited view of the entire collection is presented. Clearing that filter, by any means, pro...

That behavior is pretty confusing: having two different "default" filters when there is no filter set. Note that unset filter params is the same as pressing Cle...

what error occurs? i can't reproduce this.

job:

- 
  project: test
  loglevel: INFO
  sequence:
    keepgoing: false
    strategy: node-first
    commands:
   ...

(from [38525116c6e3d0a1ed755eea810a030c46736ce1]) Add status value to report events, update tests. [#137] https://github.com/dtolabs/rundeck/commit/38525116c6e...

Looks good.

history log of user who performed the kill currently looks like this: http://cl.ly/323F2u3G1P3X3b2G0q0w

(from [7b548d2634411cc216f5aad427af6e3a38ca470f]) Record user who performs abort/kill action for executions [#179] https://github.com/dtolabs/rundeck/commit/7b...

in the API the action is "abort" and the possible execution states include "aborted", it is not called killed.

(from [bf3b5efeeca84cb0825b76c6b1afbe74dd009543]) Improve error message printing for node dispatching. Update error message for missing keyfile [#195 state:reso...

by external history reports, I am just referring to the reports sent from outside the server into it via the log4j listener. right now it only comes from "dispa...

I agree.

Point of clarification, when you say external history reports...is this the piece where RunDeck can get log4j data from another server?

History events are logged via special log4j listener (both internally, and when running dispatch --noqueue).

this should be removed, and internal history report...

ok, perhaps change the issue to "add tags example to guide"

Ah...I was looking in the UserGuide.

-Noah

it is documented, under "tags": http://rundeck.org/docs/resource-v10.html

Add a multi-example training tutorial

Is it spaces or commas or what? Turns out to be commas, but it's not documented.

adding this to execution show page, as well as API execution info. Should this also be displayed within the History views?

(from [cceca82bc7718048f33f185eadbe14e865c1194a]) Initial api version 1 support [#137] https://github.com/dtolabs/rundeck/commit/cceca82bc7718048f33f185ea...

Versioning scheme

• Opaque version identifiers making no implication to compatibility
• Use whole numbers for version identifiers inside the URL without the use of...

I would like the behavior to be:

1. Going to the Run page means a default Node listing showing the rundeckserver with the filter preconfigured to be - "Name: {run...