Good day,
I am in the process of converting our in-progress sub-tasks to tasks due to the issues it creates on various levels of reporting and other factors.
My question is what the impact would be on any legacy sub-tasks that were done or invalid statuses if I would too disable sub-tasks in JIRA?
Regards
Lelani
Hi @Lelani Mayer ,
As far as I know Before deleting a sub-task issue type, we recommend searching for all issues of that type and bulk editing them to select another existing issue type. You can then disable the Subtask feation in configurations.
Regards
RK
Hi @Lelani Mayer ,
You can just use the bulk edit and move all sub-tasks to tasks. Once done, just remove sub-task from project issue types.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @Lelani Mayer
As per the following article, it is not possible to disable the ability to create subtasks at the global level if you currently have subtask type issues created.
https://support.atlassian.com/jira-cloud-administration/docs/configure-sub-tasks/
You would have to convert all subtask type issues to another issue type first.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you very much. I did not even think about that option instead of disabling it.
Unfortunately, I can't bulk update the conversion to a task since it loses it's parent link. I am just flushing in progress once out and still need to ensure their linked to the correct parents. But yeah when I am done with this I will remove the issue type as suggested.
Regards
Lelani
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
To remove the Subtask issue type from the project you will have to convert all the Subtasks in the project, not just the In Progress subtasks.
And when you convert them, the issue that was their parent cannot remain their parent. Issues at the same hierarchical level are siblings. One cannot be the parent of the other. You could use the generic issue linking function to add a link between the two, but Jira will not see that as a parent/child relationship.
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.