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
We are currently leveraging Automation For Jira to calculate rollups across false hierarchies (using issue links) with a created issue type (Initiative) and an existing issue type (Epic). We have a Automation for Jira Condition that calculates and rolls up Total costs on Epics to the Initiative level by using the following Smart Value:
{{#=}}{{issue.issuelinks.inwardIssue.total cost.join(" + ")}}{{/}}
Our organization reserves "is blocked by" for Initiative -> Epic links. Our calculated rollups work great if there are no other issue links on the Initiative.
The issue we are facing is that Initiatives related to each other and/or must start at specific times to each other whereby the "has to start before" and "relates to" issue links have been leveraged which renders our calculated rollups incorrect.
My Question:
Is there a way to write the Smart Value above to only look for inward issues that are of the "is blocked by" issue link type?