Our project is started in a way that Bug work item can be created under Epic items. Only item was allowed to created under the Task item is Sub Task item. How to change the project into that a Task item can have Bug items underneath it?
Thank you guys. I found that I could use the "move" operation to move the orphaned subtasks to Task items, and then define their parent to be the Epic item that was previously orphaned them while moving from a Task to Epic item. After this, a correct parent and child relationship is restored and all items under the Epic item are all Task now. I will need to label the orphaned subtasks first otherwise they will become individual tasks floating on top and hard to use bulk processing to give them a parent. I think I have a good solution now. Thank you all.
It requires a change of Hierarchy. Task and Bug are likely at the same rank.
Be warned - changing the ranking of an Issue/Work Type will likely disrupt/damage/make life very hard for you in your Jira Site. It's a global change.
Do so at your own risk and peril.
Also making a new issue type while better - adds to configuration sprawl.
You may want to consider using "Sub-Task" instead to keep things consistent - but that has its own drawbacks.
Read the fine print - carefully. Jira-Admin required.
Also notify your users if you make these changes. Check everything.
https://support.atlassian.com/jira-cloud-administration/docs/configure-the-issue-type-hierarchy/
Hi @Tim Ma,
I would not try to nest a Bug under a Task, because team-managed projects only have three levels: Epic, then standard work types like Task, Story, and Bug, then Subtask. Bug and Task sit on the same level, so a Bug can only live under an Epic or become a Subtask.
I see two practical options:
The first option is usually better for reporting: real bugs stay visible on boards and in filters, while subtasks may be hidden or grouped under their parent. Subtasks can still organize bug fixes and assign work to different people.
Hi Matthew, I guess from the title Tim Ma is in a team-managed space and changing the issue hierarchy is not global.
The work type hierarchy is set site-wide for company-managed projects, and only lets you add levels above Epic. In team-managed projects, the hierarchy is fixed per project (Epic, standard work types, Subtask), cannot be changed, and does not touch the rest of the site.
Ah - yeah Team Managed changes things.
To a point as you already pointed out.
Hi All, Thanks a lot for the responses.
Hi Martin, thanks for the suggestions. For first one, when there is no common Epic, it would seem messy. For second, when you create a new type, it is automatically placed in the same rank as "Bug, Task, …". It still could not be used under Task item. Could you further explain? Thanks.
Now that I've bothered to open my eyes a little wider - sorry about that - dug this up
https://support.atlassian.com/search-results/?searchTerm=team+managed+jira+heiarchy
It's limited - far more than I thought in comparison to Company Managed schemes.
But you may find answers.
Sadly it goes back to the same rough suggestion I gave - that you may want to consider using sub-tasks (-1 rank) to solve this.
However- sub tasks do have drawbacks in terms of what they can/can't do - but then again - it may fit the bill?
@Martin Runge
In a Team Managed project only one issue type is allowed at the Subtask level. TM projects don't support having multiple types at that level.
Hello @Tim Ma
Because you are using a TM project you won't be able to have multiple work types at the Subtask level. If you are not using Subtasks for other types of work you can use them directly to bugs.
If you already use Subtasks for other types of work then you could add a custom field to the Subtask work type and use that to categorize the Subtasks. Categorize some as Bug and others as whatever other type of work you use Subtasks to track.
Note that if you choose this path a limitation of Subtasks is that the are considered inherently part of their parent item. You can't assign them to Sprints separately from their parent item, for instance.
Hi, In a team-managed project, Bug and Task sit at the same level (level 0), under Epic and above Subtask. Work items on the same level can't be parent and child, so there's no setting that lets you create a Bug under a Task. Team-managed projects also allow only one subtask-level work type. You can rename it, but you can't add a second subtask type like "Bug sub-task". Atlassian tracks that limitation as a feature request.
Your options:
Reference: https://support.atlassian.com/jira-cloud-administration/docs/what-are-issue-types/
Thank you all for replying. Much appreciate it. I have some Task items in my project, and also there more a lot of sub tasks under each Task item. I found that I can move the Task type to Epic type. In this way I can create Bug type items at the same level as the sub tasks. This avoided having to create the Bug type under the Task type. I would like to know whether this "move" operation is safe to do. Anything I should watch out for?
When you "move" - the only risk you have to worry about is relationship linked tickets being broken.
Parent/child will break if there's a change in the hierarchy. Not to be confused with "related" links.
So long as the ranking is maintained supposedly it will be ok.
Worst case - you'll have to go back in and put the relationships back in place.
Otherwise you should be ok - aside from different work flow status or fields/screens potentially.
My advice - log the Issue Key's (ABC-123) of the tickets you are moving - go back and check them when your done moving to ensure they don't get missed.
Other pitfalls to be wary of when using the Move feature to change a Task to an Epic:
If you want to retain some indication of the original relationship between Tasks and their original Subtasks or Epics you would need to use generic work item links created between the items before you use the Move operation.
Note also that trying to find the orphaned subtasks after the fact with a JQL query does not work. If you use the query
type=Subtask and parent is empty
…it does not actually return orphaned subtasks. I had to query just for subtasks and then add the Parent column to the results display in order to find Subtasks where the Parent was missing.
Thank you all for the replies. My tasks to be moved are all top level tasks which have no parents. But they each do have a lot of subtasks. Once these subtasks are orphaned underneath each of them, search for Subtasks seemed still can find them. The subtasks should have maintained their fields, right? All searches based any field will still work, right? Is there any issue for orphaned subtasks under an Epic item? also, BTW, how to properly "log" an item and restore the item? Thanks.
I may be wrong - but the rule of thumb is this - so long as the parent doesn't become the child - or vice versa - theoretically the relationship should hold. (Or I'm blowing hot air out of my side)
Problem is Subtasks are weird and have more restrictions than your typical "parent/child" relationship
Suggestion - Test with a dummy ticket with dummy subtasks and do a move - you'll know what's what when it happens.
You may have to draw up a automation flow/rule to help do the work to keep sanity.
@Tim Ma -
As mentioned by @Trudy P Claspill especially with Team Managed project, sub-task issue type cannot live directly under the Epic issue types. In Company Manage project, yes it is possible, but it is not advisable. Epic's child tasks should be other standard issue types (i.e. Task/Bug/Story etc…) where those issue types can have sub-tasks setup.
If you are moving the Task issue type issue to an Epic issue type, I would first convert all of Task's subtask into standard issue types first. Afterward move the Parent Task into an Epic, then reassociate those subtasks (now that they are regular issue type issues) to formally roll up the new Epic issue type issue.
Hope this helps.
Best, Joseph
Hello @Matthew Sinclair
Perhaps you missed in my comment that I already did the Task/Subtask test you suggested and stated the result - the relationship is not maintained and the subtasks become orphaned. The Parent field displays no key in such work items and the are not shown in the Epic as children.
The problem with Orphaned subtasks is they are expected to have a parent item. Native Jira functionality is built around that expectation. The items may not show in agile boards without a parent. You can't assign them to sprints. They may not display when you are trying to display your items hierarchically.
You should either convert them to Tasks or move them to be child subtasks under another Task.
It looks like you're new here. Sign in or register to get started.