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
Hi team,
After the different changes related to the Parent link deprecation, I don't find a way to trigger a rule after linking a story with an epic. I have been checking the steps for Field value changed and Issue linked but it doesn't work anymore.
Do you know how it can be done?
Hi Jose,
I think you're basically running into this feature request:
https://codebarrel.atlassian.net/browse/AUT-1264
Issue hierarchy is something that's being actively worked on, on the Jira Cloud side (to make the hierarchy more generic, able to support different types of hierarchies). Once that work is complete, then we'll be able to implement this feature request more easily. We'll keep you posted.
For now you can try the work-around suggested on the issue above.
Cheers,
Andreas
My work around i use is to set a schedule for daily runs in the morning and create a variable that i can than compare or use to check/act on the parent issue using the parent.key
{{issue.Parent Link.data.key}}
I use this for my parent issuetype above Epic to be moved to a new status when the first "epic" (SAFe Feature) is moved to in progress. Helps keep my relationships in order.
I run a branch rule with the following JQL to help act on the parent.
issuetype = initiative and issuekey = {{ParentLinkDetails}}
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.