How to prevent issues from being closed while the sub-tasks are still open in Jira?
I am using "Team managed software" template.
This is NOT possible in the way you are looking for, but you can do something similar
through automation rules, but not through the rules in the workflow editor.
Instead, open your project settings and find the automation section.
You'll start on "library" tab, but you want to switch the Rules tab and then you'll be able to create one like this:
*note - you can do this in a lot of ways, I'm just choose the force the ticket back into In Progress, but you'll have to consider how you've set your project up for this to work:
To clarify, I am not "preventing" it here, that's not possible at all in Team managed projects, you need to use validators or conditionals in a Company managed project to actually prevent it, as far as I can tell.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
For a server environment (unsure if it is the same within the cloud):
If your are using Script Runner you will find a condition called
"All sub-tasks must be resolved [ScriptRunner]" while editing a transition.
otherwise it is a condition called "Sub-Task Blocking Condition". Here you can choose the status a subtask must have before the parent task can be resolved.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This is not the same in Jira Cloud for Team Managed projects.
Jira Server is similar to Jira Cloud Company Managed projects. but Team Managed projects have a very different workflow management process.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.