Feature #5484
closed
Add new issue as subtask to an existing ticket
Added by Jens Goldhammer almost 14 years ago.
Updated about 3 years ago.
Description
Subtask feature was implemented in r3573.
In comparision to Erics patch in ticket #443 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.
Maybe we can enable this field via project option.
Files
I have had several requests for this feature as well from my users.
+1
The parent ID field is only not rendered for new issues, this simple patch of the view will make it show.
Some more requests to make this fantastic tool better...
- allow setting parent issue using context menu (as in Redmine Issues Group plug-in)
- allow setting parent issue editing multiple issues (select multiple issues; set parent issue id)
This is extracted from my comment on Redmine Wiki as Eric Davis suggested after correcting some mistakes.
If you click more when editing, there is a 'parent task' field, witch allows you to set the parent task.
Eric (or JB): go for 1.0.3?
I don't really like this, there are too many things in the "new issue" view already. If you have any idea on how we could integrate this field better, I'm open to suggestions. It's just my opinion of course, no big deal if there's a consensus between other contributors to integrate it.
Jean-Baptiste Barth wrote:
I don't really like this, there are too many things in the "new issue" view already.
I agree there is a lot there but it's a field that is already present on the normal issue form. When subtasks were committed, that field was missed on new issues. Without this field, it also make the "create a new child issue" a multi step process.
I want to redo a lot of the subissue UI for 1.1, but I think Felix's patch will be fine for 1.0.3 until we come up with a better solution.
- Assignee set to Jean-Baptiste Barth
- Target version set to 1.0.3
I don't think we can say a field has been "missed" when there's a complex, explicit "unless" clause above ;-)
Anyway, I'm fine with this approach, let's include it in 1.0.3 and plan to rework on the UI for 1.1. Forgive my natural resistance to change..
- Status changed from New to Resolved
- % Done changed from 0 to 100
- Resolution set to Fixed
Committed in r4311, with additional css stuff so that you can easily hide it in your theme if you want.
- Status changed from Resolved to Closed
Merged into 1.0-stable for release in 1.0.3
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by 
Updated by 
Updated by 
Updated by 
Updated by 
Updated by