-
Suggestion
-
Resolution: Unresolved
-
None
-
5
-
14
-
Summary
The "Create a sub-task" option is available in the issue view when the issue type is configured as a level above epic (Eg Initiative)
Expected Results
Hide/remove the "Create sub-task" button from the issue view when the issue type is configured above an Epic in the Issue type hierarchy and prevent users to create subtasks in such issue types (often called Initiatives)
Actual Results
when an issue type is configured in the Issue type hierarchy above an Epic (eg. and initiative), it still shows the option to "Create a sub-task".
Workaround
Create a specific project that only contains the above Epic (or commonly Initiative) issue types as described in the documentation "Configuring hierarchy levels" under the section "Ways to set up the initiative level in plans"
- relates to
-
- Gathering Interest
-
- Gathering Interest
[JRACLOUD-89893] Remove the "Create sub-task "option in issue types above epics
Hi, this was created in response to my question.
Here is the hierarchy we have configured:
And now we see 'Create subtask' on the New Feature issue detail screen.
This is beyond confusing.
And despite the fact the subtasks are only expected under Storeis and Bugs, they can actually be created under New Features.
This reminds me of the Jira importer bug we've reported earlier, that allowed sub-tasks under Epics.
These things are so basic, it looks like Atlassian has no QA in place at all.
I do not understand why Jira developers didn't think about it when they introduced levels above epics. It absolutely does not make sense to have subtasks under initiative/theme etc.