プロジェクト

全般

プロフィール

Vote #69507

未完了

Display Issues in a hierarchy (tree)

Admin Redmine さんが3ヶ月前に追加. 3ヶ月前に更新.

ステータス:
New
優先度:
通常
担当者:
-
カテゴリ:
Issues_2
対象バージョン:
-
開始日:
2011/03/17
期日:
進捗率:

0%

予定工数:
category_id:
2
version_id:
0
issue_org_id:
7907
author_id:
15631
assigned_to_id:
0
comments:
45
status_id:
1
tracker_id:
2
plus1:
29
affected_version:
closed_on:
affected_version_id:
ステータス-->[New]

説明

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


journals

You can find similar feature request #7690, which is closed but I don't know why.
Obviously, this feature is extremely necessary.
--------------------------------------------------------------------------------
Try to *sort* the list by parent task. You should get the tree.
--------------------------------------------------------------------------------
+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.
--------------------------------------------------------------------------------
+1 I agree, we need this feature too
--------------------------------------------------------------------------------
+1 When sorting the list by parent task and then by due date, the due date sort order is ignored.
--------------------------------------------------------------------------------
I would love this feature too !
--------------------------------------------------------------------------------
+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.
--------------------------------------------------------------------------------
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...
--------------------------------------------------------------------------------
+1 I want it!
--------------------------------------------------------------------------------
+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.
--------------------------------------------------------------------------------
+1
--------------------------------------------------------------------------------
Please check my plugin - it solves this behavior:

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

--------------------------------------------------------------------------------
+1. This is very important. Can we have it in 2.4?
--------------------------------------------------------------------------------
+1 vote for it
--------------------------------------------------------------------------------
Our teams vote too. This feature can give us possibility to avoid using external reqs management tools.
--------------------------------------------------------------------------------
+1.
We are using "Vitaly Klimov":/users/6870 "Smart Sort":/plugins/redmine_smart_issues_sort plugin, but would like to reduce dependencies.
--------------------------------------------------------------------------------
+1.
... Smart Sort plugin crashed on Redmine 2.3.2 (ruby 1.9.3)
--------------------------------------------------------------------------------
+1 because sorting via the additional parent item column steals available monitor space.
--------------------------------------------------------------------------------
+1
--------------------------------------------------------------------------------
+1
--------------------------------------------------------------------------------
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.
--------------------------------------------------------------------------------
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.
--------------------------------------------------------------------------------
+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.
--------------------------------------------------------------------------------
Is it that hard? I see open tickets for 4+ years

--------------------------------------------------------------------------------

--------------------------------------------------------------------------------

--------------------------------------------------------------------------------

--------------------------------------------------------------------------------

--------------------------------------------------------------------------------

--------------------------------------------------------------------------------
+1
--------------------------------------------------------------------------------
+1
--------------------------------------------------------------------------------
+1
A patch would be enough
--------------------------------------------------------------------------------
+1
6 years after report....
--------------------------------------------------------------------------------
+1
--------------------------------------------------------------------------------
A custom query with @Parent task@ as first order does the trick for me (no need to put it on the columns)
--------------------------------------------------------------------------------
+1
Very usefully
--------------------------------------------------------------------------------
+1
--------------------------------------------------------------------------------
+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.
--------------------------------------------------------------------------------
+1
Please fix this issue. We need this.
--------------------------------------------------------------------------------
+1
--------------------------------------------------------------------------------
+1
We are using Vitaly Klimov Smart Sort Plugin. We want to upgrade, but the Plugin is not working with 4.1.
--------------------------------------------------------------------------------
Klaus Adler wrote:
> +1
> We are using Vitaly Klimov Smart Sort Plugin. We want to upgrade, but the Plugin is not working with 4.1.

As far as the tree view is concerned you may have a look at this plugin here: https://www.redmine.org/plugins/redmine_issues_tree

--------------------------------------------------------------------------------
+1
--------------------------------------------------------------------------------
+1
--------------------------------------------------------------------------------
+1
--------------------------------------------------------------------------------


related_issues

relates,New,6116,Group sub-tasks with parent on issue list
relates,New,10048,Secondary sorting after sorting by parent task
relates,New,5275,Show tree of issues instead of a list in Roadmap
relates,New,6320,Subtasks do not appear under parent task in Issues view
duplicates,Closed,10296,parent-child relation in issue list
duplicates,Closed,7417,parent issue display problem
duplicates,Closed,12648,Multiple levels of nested subtasks not displayed correctly in issue list
duplicates,Closed,20099,subtask can't listed under the father issue

Admin Redmine さんが3ヶ月前に更新

  • カテゴリIssues_2 にセット

他の形式にエクスポート: Atom PDF

いいね!0
いいね!0