Project

General

Profile

Actions

Defect #5480

closed

Missing features of subtask implementation (r3573)

Added by Jens Goldhammer over 14 years ago. Updated over 14 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
2010-05-09
Due date:
% Done:

0%

Estimated time:
Resolution:
Invalid
Affected version:

Description

There are three features I miss in the current implementation of the subtask feature (r3573) in comparision to Erics patch in ticket #443.

- the issue hierachy in the issue view is missing. An overview of all substasks for one issue is very good in my eyes because you can edit them very easily and you get a good impression of all tickets belonging to the ticket! Maybe a kind of folding can be implemented to allow loading subtasks in a deeper hierachy via ajax.
- the autocompletion feature to add a new issue as a child of another issue. In the current trunk the user has to manually enter the id of the ticket.
- The current implementation does not allow to add a new issue as child to an existing ticket in the ticket view. You always have to navigate to the parent issue and than add a child issue. This increases the amount of clicks the user has to do.

Any reason why not integrating this into the current trunk?

Thanks,
Jens


Files

completion.png (3.3 KB) completion.png Jean-Philippe Lang, 2010-05-09 13:08
Actions #1

Updated by Jean-Philippe Lang over 14 years ago

Jens Goldhammer wrote:

- the issue hierachy in the issue view is missing. An overview of all substasks for one issue is very good in my eyes because you can edit them very easily and you get a good impression of all tickets belonging to the ticket! Maybe a kind of folding can be implemented to allow loading subtasks in a deeper hierachy via ajax.

See #5196. Please submit any improvement suggestions as a feature request.
Maybe we could display the issue tree by default when sorting by issue id.

- the autocompletion feature to add a new issue as a child of another issue. In the current trunk the user has to manually enter the id of the ticket.

Somewhat related to the point below, but autocompletion is implemented:

- The current implementation does not allow to add a new issue as child to an existing ticket in the ticket view. You always have to navigate to the parent issue and than add a child issue. This increases the amount of clicks the user has to do.

I did not want to add another field to the new issue form in order to keep it simple. For example, Jira works like this.
Please, fill a feature request if you really need this.

Actions

Also available in: Atom PDF