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
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
I have Story issues created across different epics and sprints. They are related in some fashion. I want to automate the proceess of editting the Flagged: field and attach the same value to all linked issues after setting Flagged: to a value. I also want this automation rule to execute in reverse.
Here is my example:
Issue #1, Epic #1, Sprint 1 (blocks Issue #2 and Issue #3)
Issue #2, Epic #2, Sprint 2 (blocked by Issue #1, blocks Issue #3)
Issue #3, Epic #3, Sprint 3 (blocked by Issue #1 and Issue #2)
When I edit Issue #1, Flagged: = "some value"
I need the automation to execute and attach the same Flagged: value to Issue #2 and Issue #3.
I attempted to build this rule out, but the JQL doesn't seem to be able to find the two linked issues.
Hi @lintek214 - You should be able to do something like this:
Note - If your rule is cross-project, you'll need to update Rule Details >> Project Scope to either global or the specific projects. This can be done in System >> Global Automation.
Thanks, that me help tremendously! I have one more question. Does Jira automation support "chain modification logic" in the automation rules? Using my case above in a different way:
Issue #1, (blocks Issue #2)
Issue #2, (blocked by Issue #1, blocks Issue #3)
Issue #3, (blocked by Issue #1)
If I edit Flagged: for Issue #1, I want Flagged: to change for Issue #2 and "through the chain" Flagged: for Issue #3
This one may be a little more tricky. You could try activating
Check to allow other rule actions to trigger this rule. Only enable this if you need this rule to execute in response to another rule.
Theoretically, as each issue is flagged, it would re-trigger the rule for each subsequent flag, but I haven't tried it and if it does work, you'll need to be careful about how far the daisy chain goes because you could run into some throttling issues.
EDIT - I don't think this will work. I don't think a rule can trigger itself. You'd probably want to set an extra action to add a label to all of the issues that were flagged and then have another rule that triggers on field value changed (labels). At the end of the second rule, you'd remove the labels.