Frontend. Jobs don't group?
-
Alex-SF
- Assigned user set to Alex-SF
-
Greg Schueler
if there were any jobs under System/ then it would break apart in the way you describe.
if there are no jobs in any of the higher-level groups, then they will fold up to preserve space.
-
Greg Schueler
- State changed from new to invalid
-
Alexei Bratuhin
Hello all,
I personally find, that in the following scenarioA/C/X/Y/Z
A/C/X1/Y1/Z1
A/D/X/Y/Z
A/D/X1/Y1/Z1
B/C/X/Y/Z
B/C/X1/Y1/Z1
B/D/X/Y/Z
B/D/X1/Y1/Z1splitting job groups by "/" to represent each group as a tree node would result in a better overview and usability.
If you are not going to include this presentation as option into the main branch of the software, probably you could give me a clue, what code has to be changed to implement this behaviour?
Regards.
-
Greg Schueler
- Tag set to feature request, gui
- Milestone set to Rundeck 1.3
- State changed from invalid to open
- Assigned user changed from Alex-SF to Greg Schueler
- Milestone order changed from 7 to 0
re-opening this issue as "real-tree" view issue.
ref pull request for issue #254 Inconsistent job/group behavior
-
Deleted User
- State changed from open to needs_verification
(from [9386ca0573e34a41afb68cef04007dc6e287035a]) Make tree view for job groups the default [#162 Frontend. Jobs don't group? state:needs_verification] https://github.com/dtolabs/rundeck/commit/9386ca0573e34a41afb68cef0...
-
Greg Schueler
The real job tree can be toggled with the "rundeck.gui.realJobTree" (true/false) setting in rundeck-config.properties.
the default is "true"
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.