Troubleshooting Smart Values in Epic Automation for Story Point Aggregation

[Antoni Bobiński]

Hello everyone!

I'm currently working on setting up an automation to aggregate story points from stories within an Epic, but I'm encountering issues with my smart values.

When I use the JQL search query: "Epic Link" = "{{issue.epic name}}", I receive the message: "No issues have a parent epic with key or name '{{issue.epic name}}'."

However, I have linked child issues as Stories under Epics.

Does anyone have any insights into why this might be happening?

[Marc -Devoteam-]

Hi @Antoni Bobiński 

Welcome to the community.

You can make an automation rule for this option.

[John Funk]

Hi Antoni - Welcome to the Atlassian Community!

First, the Epic Link is a key value and not a name. So the Epic Link would never equal the Epic Name. 

Second, the Epic Link field is going away. You should use the parent field. 

Please share a screenshot of your rule so that we can help you better (after making the changes above). 

[Eugenio Onofre]

Hello @Antoni Bobiński

Welcome to the Atlassian Community.

The Epic Link and Parent Link fields in Jira Cloud are being deprecated, which will impact how these smart values are used.
https://support.atlassian.com/jira-software-cloud/docs/upcoming-changes-epic-link-replaced-with-parent/#Updates-to-automation

Please consider using {{issue.parent.key}}

Please remember to accept this answer in case it helps you resolve your question as it may also help other community members in the future.

Regards,
Eugenio