Feature #7907

Display Issues in a hierarchy (tree)

Added by Wael Nasreddine over 8 years ago. Updated 9 days ago.

Status:NewStart date:2011-03-17
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:Issues
Target version:-
Resolution:

Description

Hello,

We have setup issues and child issues, for example, to complete a big task, we divide it into many small tasks, the parent task being the big one.

However the view on the issues page is not very informing even with the column parent task activated, what would be interesting is having a tree-like representation of the tasks.

is this possible?

Regards,
Wael Nasreddine


Related issues

Related to Redmine - Feature #6116: Group sub-tasks with parent on issue list New 2010-08-12
Related to Redmine - Defect #10048: Secondary sorting after sorting by parent task New
Related to Redmine - Feature #5275: Show tree of issues instead of a list in Roadmap New 2010-04-08
Related to Redmine - Defect #6320: Subtasks do not appear under parent task in Issues view New 2010-09-07
Duplicated by Redmine - Feature #10296: parent-child relation in issue list Closed
Duplicated by Redmine - Defect #7417: parent issue display problem Closed 2011-01-23
Duplicated by Redmine - Defect #12648: Multiple levels of nested subtasks not displayed correctl... Closed
Duplicated by Redmine - Defect #20099: subtask can't listed under the father issue Closed

History

#1 Updated by Sergey Ratz about 8 years ago

You can find similar feature request #7690, which is closed but I don't know why.
Obviously, this feature is extremely necessary.

#2 Updated by Jean-Philippe Lang about 8 years ago

Try to sort the list by parent task. You should get the tree.

#3 Updated by Ruedi Silvestri over 7 years ago

+1 would be extremely helpful. Sorting does not really help as you do not see the parent next to the child. Further in case you have more than one layer of hierarchy sorting doesn't work anymore at all.

#4 Updated by Oleg Chunikhin over 7 years ago

+1 I agree, we need this feature too

#5 Updated by Mario Lipinski over 7 years ago

+1 When sorting the list by parent task and then by due date, the due date sort order is ignored.

#6 Updated by György Kiss over 7 years ago

I would love this feature too !

#7 Updated by K. Scott Tripp over 7 years ago

+1 This would be extremely useful.

Without it larger projects that need formal requirements tracking would depend on systems like DOORS or CRADLE,
which is unfortunate because has the core functionality needed to replace them.

#8 Updated by K. Scott Tripp over 7 years ago

My bad for double post, but I can't seem to edit my own posts.
I meant to say

...unfortunate because redmine has the core functionality...

#9 Updated by Sang-jae Shin over 7 years ago

+1 I want it!

#10 Updated by Daniel Albuschat over 7 years ago

+1
For me, this is a big issue, too.
IMHO, the logic of the issue list should be changed to behave like this:

UI changes:
  • Add a checkbox whether the changes described here should be applied, named something like "Show subtasks in tree view" (even without sorting by parent task). Default: Yes
  • Add a checkbox whether the filter criteria should be applied to subtasks, too. It is surely not uncommon that you would like to filter parent tasks by priority, for example, but have all subtasks of these filtered tasks visible. Sometimes, however, you probably just want to see subtasks with the same, filtered priority.
Logic changes:
  • Change the issue list to filter only parent tasks.
  • For each parent tasks, filter the corresponding subtasks and display them below (and indented to) the parent task
  • The same procedure is done recursively for the subtasks' subtasks, too.

Optimizations:
There are two ways to avoid multiple database queries for each parent task:
a) select a field has_subtasks as "case when exists (select * from issues subissue where subissue.parent_id=issue.parent_id) then 1 else 0 end as has_subtasks". With this, you can check whether you need to query for subtasks at all without executing another query.
b) Add a field "has_subtasks" in the table issues that is automatically updated by a trigger when a subtask has been added or removed (this makes updating a little bit slower, but selecting the issues much faster - especially for lists without or with a only a few subtasks)

What do you think, Jean-Philippe Lang?
Since this is a big issue for me (I just introduced Redmine in our company), I'd even try to implement this.

#11 Updated by Stéphane Thomas over 7 years ago

+1

#12 Updated by Vitaly Klimov over 7 years ago

Please check my plugin - it solves this behavior:

http://www.redmine.org/plugins/redmine_smart_issues_sort

#13 Updated by Dipan Mehta about 6 years ago

+1. This is very important. Can we have it in 2.4?

#14 Updated by Anton Potapov about 6 years ago

+1 vote for it

#15 Updated by Mikhail Pirogkov about 6 years ago

Our teams vote too. This feature can give us possibility to avoid using external reqs management tools.

#16 Updated by @ go2null about 6 years ago

+1.
We are using Vitaly Klimov Smart Sort plugin, but would like to reduce dependencies.

#17 Updated by Pavel Z over 5 years ago

+1.
... Smart Sort plugin crashed on Redmine 2.3.2 (ruby 1.9.3)

#18 Updated by Anonymous over 5 years ago

+1 because sorting via the additional parent item column steals available monitor space.

#19 Updated by Sergiy Nazarov over 5 years ago

+1

#20 Updated by Kaskade LNA over 5 years ago

+1

#21 Updated by Ofer Nave about 5 years ago

Yes, I would very much like this, too.

Right now, if a subtask happens to end up in the row following the parent task, it is indented with a right arrow icon, which is very nice. But otherwise, nothing.

#22 Updated by Ofer Nave about 5 years ago

According to #6116, you can achieve correct hierarchial sorting (between parent and subtasks) by creating a custom query that sorts on "Parent task", "ascending".

However, then you effectively can't sort by anything else, like priority or status.

#23 Updated by Robert Schneider about 5 years ago

+1 too.

The gantt diagram already contains it. But it is not enough.

I would create a new view for this. When the user is in the Tickets tab he or she should get the option to display the (existing) list view or the tree view. I think a tree view has the same value as a list, though they may provide different functions. Ideally, tree view and list view should be one thing. But this could be difficult to implement. That's why suggest to start a new view. A primitive tree view is better than no view.

#24 Updated by Jorge S. over 4 years ago

Is it that hard? I see open tickets for 4+ years

#25 Updated by Toshi MARUYAMA over 4 years ago

  • Related to Feature #5275: Show tree of issues instead of a list in Roadmap added

#26 Updated by Toshi MARUYAMA over 4 years ago

  • Related to Defect #18068: Copying Projects & Parent Child Issues added

#27 Updated by Toshi MARUYAMA over 4 years ago

  • Related to deleted (Defect #18068: Copying Projects & Parent Child Issues)

#28 Updated by Toshi MARUYAMA over 4 years ago

  • Related to Defect #6320: Subtasks do not appear under parent task in Issues view added

#29 Updated by Toshi MARUYAMA almost 4 years ago

  • Duplicated by Defect #20099: subtask can't listed under the father issue added

#30 Updated by Sergey Startsev over 2 years ago

+1

#31 Updated by Emanuel Reisinger over 2 years ago

+1

#32 Updated by Stefan Lindner over 2 years ago

+1
A patch would be enough

#33 Updated by Alexander Scherdo almost 2 years ago

+1
6 years after report....

#34 Updated by jiangshan song almost 2 years ago

+1

#35 Updated by Pierre de LESPINAY over 1 year ago

A custom query with Parent task as first order does the trick for me (no need to put it on the columns)

#36 Updated by Alessandro Zucchi over 1 year ago

+1
Very usefully

#37 Updated by Tomaž Šuštar about 1 year ago

+1

#38 Updated by Entwicklung AMIT about 1 year ago

+1
What's about this feature 7 years ago since now?
Support sorting in issue-query by parent task (field) AND an other field in order to sort within the parent fields comes to be very important. Thanks for regard this request.

#39 Updated by Manzumul Haque 7 months ago

+1
Please fix this issue. We need this.

#40 Updated by Claudio Negri 9 days ago

+1

Also available in: Atom PDF