It's not the same without you
Join the community to find out what other Atlassian users are discussing, debating and creating.
Hi,
How do you prevent a parent issue (Mostly of type Story) from closing if it has got any child issue (of type: Sub-task, Bug or task etc) associated with it. I know of a plugin (JIRA Workflow Toolbox) which lets me do that but I do not want to use it for obvious reasons . Is there any way this can be achieved without using any plug-in.
Can any one help on this?
Thanks,
Hitesh
There is a built in condition for "prevent this transition if any subtasks are in <list of> status". Try that one.
Thanks Nic, but this condition is only for sub-tasks. There could be issues of other type as well which are not being taken care of by this condition.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I think you've misread it - it's for all sub-task types. Doesn't matter what they're called.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I think Hitesh means that you can link an issue using the "is parent of" and "is child of" links without them being sub-task types.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Then they're not sub-tasks. Those are link types that are not off-the-shelf, so they've been added by an admin, and they're frankly meaningless because they don't define sub-tasks. They are links, and they do define a relationship, but it's not parent/child, it's parent/parent with a misleading name.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I'm fully aware of all of that, the question of how to check the status of linked issues is still perfectly valid in general I think. I've found another question that deals with this quite nicely: https://answers.atlassian.com/questions/159524
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...
Connect with like-minded Atlassian users at free events near you!
Find a groupConnect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.
Start an AUGYou're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.