[#JRA-5617] Change a sub-task to be a normal issue

JIRA

Change a sub-task to be a normal issue

Created: 09/Jan/05 12:06 AM Updated: 12/Apr/07 09:00 PM

Component/s:

Sub-tasks

Affects Version/s:

3.0.2

Fix Version/s:

3.9

Time Tracking:

Not Specified

Issue Links:

Duplicate

This issue is duplicated by:

~~JRA-10963~~ Add ability for a sub-task to be moved from PROJECT-A to another project (eg PROJECT-B) as an item that does *** NOT *** have a PARENT ITEM in PROJECT-B

~~JRA-9442~~ Ability to select any "sub-task item" in JIRA and have the ability to "promote" it so it is no longer a sub-task item. Having a "promote" button on the far left similar to "Clone" etc would be nice.

~~JRA-5736~~ Convert subtasks to top level tasks

~~JRA-9999~~ Changing a subtask to a task and vice-versa

~~JRA-9742~~ Promote Sub-Tasks to Tasks

~~JRA-8728~~ Promote Sub-tasks to become an Issue

Reference

This issue relates to:

~~JRA-5410~~ Subtaskify issues

This issue is related to:

JRA-4446 Sub-issues should be able to contain their own sub-issues

Participants:	Ahmad Masrieh, Carl Hoeg, Chris Boulter, Colin Bendell, Eric Broyles, Joshua Spiewak, Melissa, Michelle de Guzman, Mick Hollins, Nick Menere [Atlassian] and Scott Farquhar [Atlassian]
Since last comment:	1 year, 18 weeks, 4 days ago
Resolution Date:	12/Apr/07 09:00 PM
Labels:

Description

« Hide

I would like to be able to convert a sub-task into a normal issue. The reasons are that

sometimes issues are created as sub-tasks when they should not be.
sometimes a sub-task outlasts the issue for which it is a sub-task and it needs to become a task of its own

Currently the workaround is to close the issue and open a new issue, but this is not ideal, as the issue ID changes rendering any links to the issue dangling.

All

Comments

Work Log

Change History

Sort Order:

[ Permlink | « Hide ]

Carl Hoeg added a comment - 28/Jan/05 02:48 AM

I need to move subtasks from one project (support) to another (development). JIRA support says I need this issue to be able to do it, so please build it!

[ Permlink | « Hide ]

Joshua Spiewak added a comment - 16/Jun/05 02:14 PM

Presumably once this issue and ~~JRA-5410~~ are implemented, it will also be possible to change the parent issue of a sub-task, e.g. a situation where a sub-task is mistakenly created off of the wrong top level issue.

[ Permlink | « Hide ]

Ahmad Masrieh added a comment - 16/Nov/05 06:31 AM

Please review this post

_http://forums.atlassian.com/thread.jspa?threadID=9146_

and consider this issue as a part of a greater whole.

Ahmad

[ Permlink | « Hide ]

Melissa added a comment - 02/Jun/06 12:10 PM

The post Ahmad linked to seems to be gone now. My group also needs the ability to promote a sub-task to its own task.

[ Permlink | « Hide ]

Ahmad Masrieh added a comment - 02/Jun/06 01:24 PM

Melissa, unfortunately I appended by mistake a '_' character to the URL – this leads to a dead link

And because of ~~JRA-1100~~, I'm not able to correct all posts with the wrong URL

Use this corrected link ( http://forums.atlassian.com/thread.jspa?threadID=9146 ).

Ahmad

[ Permlink | « Hide ]

Eric Broyles added a comment - 14/Jun/06 08:06 AM

Would this mean that since sub-tasks/issues would now be full issues that you could create a sub-issue of a sub-issue? For example, assume issue EX-12 with sub-issue EX-34. Since EX-34 is a normal JIRA issue (even though it is a sub-issue of EX-12) it can have sub-issues itself. So EX-34 could have sub-issue EX-56.

Am I understanding this correctly? We find ourselves needing to create sub-issues of sub-issues, allowing us to manage very high-level requirements (CEO/CIO level), more organizational requirements (director/manager level) and the granular technical requirements (developer/tester level).

[ Permlink | « Hide ]

Colin Bendell added a comment - 04/Aug/06 12:26 PM

Yes, Eric this is exactly what we desire. In fact you could even think of a versions as a giant parent task. In our organization we develop release requirements which basically summarise the tasks and provides extra information about how the tasks interconnect, etc. You could easily imagine a version being another form of issue to which you move through the life cycle of the product, comment on, and watch (a simplified form of a subscription).

[ Permlink | « Hide ]

Scott Farquhar [Atlassian] added a comment - 29/Aug/06 09:03 PM

~~JRA-10963~~ also wants to promote and move to a new project at the same time.

[ Permlink | « Hide ]

Chris Boulter added a comment - 24/Nov/06 10:52 AM

Also vice versa (change a normal issue to be a subtask), This would be useful if you add an issue, but then realise it is part of some larger issue.

[ Permlink | « Hide ]

Michelle de Guzman added a comment - 26/Nov/06 07:45 PM

Chris,

That feature is currently being tracked at JRA-5410.

Please comment/vote/watch the issue for any further developments.

–
Cheers,
Michelle

[ Permlink | « Hide ]

Nick Menere [Atlassian] added a comment - 12/Apr/07 09:00 PM

Hi guys,

This issue has been completed and will ship in 3.9.

Enjoy!!

Cheers,
Nick