rundeck job groups and organization

[Charles Scott]

Using rundeck 1.2.1

Should't each job be listed so that you need to drop down its parent group before seeing sub groups?

[deploy@dev-ctier1 stg]$ grep '<group' stgAtg.xml
<group>Staging/Commerce</group>
<group>Staging/Commerce</group>
<group>Staging/Commerce</group>
<group>Staging/Commerce</group>
<group>Staging/Commerce</group>
<group>Staging/Commerce</group>

[Robert Krombholz]

Hi Charles,

we had the same topic already.
This basically happens whenever you have "empty" subgroups.

Please have a look at this ticket.
http://rundeck.lighthouseapp.com/projects/59277/tickets/254-inconsistent-jobgroup-behavior

The ticket needs some verification as I created a pull request while
this was already partially fixed.
Don't know whether the team wants to include the configurable real tree
behavior for the Jobs page that was part of my pull request.

Cheers
Robert

[Greg Schueler]

looking at the issues, i think we can put the "real tree" in its own issue.

actually, there is an older issue here http://rundeck.lighthouseapp.com/projects/59277/tickets/162-frontend-jobs-dont-group

i think that was incorrectly marked "invalid"  he is asking for the "Real tree" view

I'm going to re-open it and reference your pull request to fix it

[Greg Schueler]

Can I call for a vote regarding how to display the Job Groups by default?

A: current system.  As few groups are shown as possible, so no empty groups are present.

B: tree view. The groups are displayed accurately as a tree, including empty intermediate groups. (Robert Krombholz's patch)

The usability differences are that choice A) has fewer clicks necessary to view jobs that are perhaps several groups deep, but B) accurately reflects the group organization.

Note that both displays will be available as a configuration option, but a vote is the default configuration.

To vote just reply with A or B.

See screenshots:

A: 

B:

[Chuck Scott]

Hi Greg,

I vote B

My reasoning is based on migrating from ctlcenter and appears more natural. 
Sent from my iPhone

On Jun 9, 2011, at 5:09 PM, Greg Schueler <gr...@controltier.com> wrote:

Can I call for a vote regarding how to display the Job Groups by default?

A: current system.  As few groups are shown as possible, so no empty groups are present.

B: tree view. The groups are displayed accurately as a tree, including empty intermediate groups. (Robert Krombholz's patch)

The usability differences are that choice A) has fewer clicks necessary to view jobs that are perhaps several groups deep, but B) accurately reflects the group organization.

Note that both displays will be available as a configuration option, but a vote is the default configuration.

To vote just reply with A or B.

See screenshots:

A: 

<Screen shot 2011-06-09 at 5.04.14 PM.png>

B:

[Kaizer Sogiawala]

+1 on B

[Kaizer Sogiawala]

I'd also like to see a "Search" enabled for job ;-)

[Moses Lei]

I say B but with this qualification:

I think B is better only if rundeck remembers on a per-user basis what groups were open the last time they logged in.

Moses

--
Moses Lei
[ Professional Services | DTO Solutions, Inc. ]
[ mobile: 703.901.5969 | e-mail: ml...@dtosolutions.com | aim/gtalk: ml...@controltier.com | yahoo: moseslei | windows live (msn): ml...@dtosolutions.com ]

[Greg Schueler]

i think we have 5+ votes for B and 0 for A right now, so i'm going to make the real tree the default setting.

It would be nice to have more personalized customization of the GUI, but that is another issue...