nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Lookup Issues - The option "our issue key" for field 'Epic Link' does not exist.

Abhishek_Ajmera

I am trying to create a rule where trigger is any change to story points field on a story or task.

Action in this case is to update the Epic of the issue to have the sum

In the Lookup Issues, I have put the JQL "Epic Link" = {{issue.key}}

and then edit issues fields I try to update "Story Points" = {{lookupIssues.Story Points.sum}}

It always throws an error "The option "our issue key" for field 'Epic Link' does not exist." I can see on all our issues we have the epic link field showing up details section.

What am I doing wrong in this?

Or is there an alternative to doing this?

Accepted answers

All comments

Fabian Lim

Hi @Abhishek_Ajmera

Take a look at this post: https://community.atlassian.com/t5/Automation-articles/Jira-Automation-Sum-Up-Story-Points-Roundup-Initiatives-gt-Epics/ba-p/1928027

Regards

Abhishek_Ajmera

Thanks for quick response and thanks for this link, did not know that issue.Epic Name was also a smart value available. But still i see similar error, previously I was getting "The option "our project epic key" for field 'Epic Link' does not exist."

now I get "The option "our project Epic Name" for field 'Epic Link' does not exist."

Stefan Salzl

Hi @Abhishek_Ajmera ,

Could you add a screenshot of your automation rule and the audit log output? This would help get a better overview of the setting and identify the problem to find a fitting solution.

Thanks in advance.

Best
Stefan

Abhishek_Ajmera

Thanks for the response @Stefan Salzl I am adding the rules and the screenshots

Screen Shot 2022-02-19 at 12.18.56 PM.png

Error:

Screen Shot 2022-02-19 at 12.36.26 PM.png

The project that it picks is correct, the issue keys that it is showing is correct but I keep receiving this error.

Fabian Lim

Check if the stories in the epic come from the same project. If you are picking tickets from another project you will have to make it global.

Regards

Stefan Salzl

As @Fabian Lim already mentioned in the answer below:

The very first line of the audit log gives the information that the rule is limited to one project (single project rule). Therefore only issues within this project can be considered for further processing within the rule.

In case issues to be fetched/looked up exist in other projects the rule has to be a multi project or global rule. This can be configured via:

Rule details --> Scope

Best
Stefan

Abhishek_Ajmera

@Fabian Lim is there a specific way to look at the project details? From the breadcrumb at the top, both the epics and the stories in the epic are all part of the same project.

What do you mean when you say "you will have to make it global"

One thing to note is that the parent of the epic (an Initiative) is from a different project.

Abhishek_Ajmera

Yes thanks for the hint @Fabian Lim and @Stefan Salzl

I looked at this option of creating global rules, but does that mean that this rule will start applying to all the projects? That is something I don't want to do or own as almost every team/project we have in Jira uses jira differently.

Bill Sheboy

Hi @Abhishek_Ajmera

Are you using a company-managed or a team-managed project for these issues and rule? I ask because:

company-managed projects link epic/children with the "Epic Link" field and use the "Story points" field
team-managed ones use "parent" and "Story point estimate"

That would impact both the rule test conditions and the JQL used for Lookup Issues. And note that the spacing and capitalization are important for smart values, so confirm you have the correct values to get rules to work.

When in doubt, use this how-to article to confirm the exact names of the smart values to use for your project's issues: https://support.atlassian.com/cloud-automation/docs/find-the-smart-value-for-a-field/

Kind regards,
Bill

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

automation