You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Hi,
I have a question that goes against the grain of what is usually asked about:
It's possible that when the issue PARENT is closed, automatically all your issues CHILD will be closed with the same resolution?
Example:
I had a massive incident that generated 100 tickes (child's). They are linked to the issue parent, so, when the issue parent problem is solved, the children's problems should be solved automatically with the same resolution.
It's possible?
Cheers,
Leticia
Thanks for the feedback!
I managed to get close to something similar, however, I am having trouble replicating the resolution (description of the solution):
Would that be a New Action?
Yea, add a new action before the transition that sets the resolution. The other option would be to remove resolution from the transition screen used in the workflow and instead use a post function that sets the resolution.
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.
Welcome to Atlassian Community!
Yes, this can easily be done using Automation, there is actually one in the Automation library that you can use. It looks like this:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Would this work for other issue types such as requirements? Or would it only work for sub-tasks? If a story was a parent to several requirement issue types would it be possible to utilize the same rule?
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.