Hi all,
In Jira cloud, sub-tasks cannot be created under the issues at the level of Epics and above. They are always can be added under the issues which are at the level Story, Task, Bugs etc.
However, I have observed in Jira data center, you can create sub-tasks under the Epics as well. Even if you create an issue type above the 'Epic' level (via Jira Plans/Advanced roadmaps), those higher level issue types also allow creation of sub-tasks under them.
I want to know if this is a bug or it is by design. If by design, what is the utility of this? How often teams use this structure and is there a way to disable it.
Thanks in advance.
Regards,
Sujeet
This is as designed by Atlassian in the latest issue view, in the previous issue view, this could be done.
See also; JRACLOUD-72060
If I'm not wrong, you are looking at Jira cloud.. My query is specific to Jira Data Center.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The function in DC is as designed.
As mentioned, this function worked in Cloud as well, but on Cloud this has changed,
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Please see this older question for the same idea, including a 20 year old suggestion to add that feature:
Kind regards,
Bill
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.