Feature #5275
open
Show tree of issues instead of a list in Roadmap
Added by Alex Last almost 16 years ago. Updated over 2 years ago.
Description
Since we have "subtasks" now, it would be better to (optionally) show a tree of issues in the "Roadmap" instead of a list of issues.
Is there an overall design ready how subtasks will affect the user interface in general?
Files
| change_roadmap_issues_to_tree_structure.patch (4.88 KB) change_roadmap_issues_to_tree_structure.patch | Mizuki ISHIKAWA, 2018-11-08 02:40 | ||
| before_change.png (63.5 KB) before_change.png | Mizuki ISHIKAWA, 2018-11-08 02:40 | ||
| roadmap.png (126 KB) roadmap.png | Mizuki ISHIKAWA, 2018-11-08 02:40 |
Related issues
Updated by Mischa The Evil about 15 years ago
- Subject changed from show tasks tree, not list in Roadmap to Show tree of issues instead of a list in Roadmap
- Category changed from UI to Roadmap
Updated by 
Updated by
Updated by Sergey Ratz almost 15 years ago
Why this ticket is closed?
It should be opened.
Updated by 
Updated by 
Updated by
Updated by Fede Garcia almost 14 years ago
Is there any plan to implement this request?
Are there plugins (compatible with the latest version of redmine) providing this feature?
Cheers
Updated by Daniel Albuschat almost 14 years ago
This is in some way related to #7907. IMHO, the ticket list in the Roadmap should be replaced by - or at least made more similar to - the "normal" ticket list.
Updated by 
Updated by 
Updated by 
Updated by
Updated by Ben Flaumenhaft over 11 years ago
See here as well --
See http://www.redmine.org/projects/redmine/wiki/HowTo_TreeQuery
Updated by Toshi MARUYAMA over 11 years ago
- Related to Feature #7907: Display Issues in a hierarchy (tree) added
Updated by
Updated by Mizuki ISHIKAWA over 7 years ago
- File change_roadmap_issues_to_tree_structure.patch change_roadmap_issues_to_tree_structure.patch added
- File roadmap.png roadmap.png added
- File before_change.png before_change.png added
I propose to change the order of issues in the roadmap in ascending order of Parent task.
The result of applying the patch:
before change:
Updated by Go MAEDA over 7 years ago
Currently, issues on the Roadmap page are sorted by tracker_id. You can see an example on https://www.redmine.org/projects/redmine/roadmap. As a committer of Redmine, the order is convenient. This is the similar order with the Changelog.
But the patch change_roadmap_issues_to_tree_structure.patch sorts issues by issues.id. I don't like the order.
Updated by Go MAEDA about 7 years ago
- Has duplicate Feature #16026: Roadmap subtask added
Updated by Jeremy D about 7 years ago
I applied the patch provided in #5275-19 and found it extremely helpful. It's not clear to me why it would be a desirable behavior to order by issue number; the order in which an issue is created (and thereby receives a number) has no necessary and sufficient bearing on due date nor relationships with other trackers, which seem like defining characteristics of a roadmap.
A cursory google search seems to indicate that this is a highly requested feature, and Mizuki ISHIKAWA's solution seems to work. Thanks very much.
Updated by
Updated by David L over 2 years ago
+1 This would be extremely helpful!
I'm not sure how much the sorting matters but can we get a patch that keeps the default tracker_id sorting?
Updated by David L over 2 years ago
Mizuki ISHIKAWA Can you change the default sort of the patch? Is there a help page that could tell me how to apply the patch to a Docker deployment?
Updated by Mizuki ISHIKAWA over 2 years ago
David L wrote in #note-24:
+1 This would be extremely helpful!
I'm not sure how much the sorting matters but can we get a patch that keeps the default tracker_id sorting?
For the same reasons as 10048, it is difficult to achieve a parent-child structure and other orders at the same time, IMO.
Sorry I can't help you.
David L wrote in #note-25:
Mizuki ISHIKAWA Can you change the default sort of the patch? Is there a help page that could tell me how to apply the patch to a Docker deployment?
This is an old patch and I would not recommend applying it. There is also a risk that if it does work, it is likely to stop working with future versions.
General patching procedures: Patch