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?