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?

[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

[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

Error:

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

[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]

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.

[Stefan Salzl]

In general: the scope of the rule is than global, yes.

The rule can also be configured as a multi project rule including only several projects to which the rule should have access to.

does that mean that this rule will start applying to all the projects

As said before: the scope applys then to all projects. In case the rule is not expected to be triggered from all projects activation/processing can be limited with a condition after the trigger (see screenshot)

Hope this helps.

Best
Stefan

[Abhishek_Ajmera]

I will give this a shot but it does not feel like at least my issue was project scope as I re-verified the test epic and the stories under that epic are all from the same project so theoretically I should not need a global rule.

[Stefan Salzl]

Might it be possible to see the whole error message? And if possible also the configuration lookupIssue action to find out what happens in the processing of the JQL (as it seems something is going wrong there).

[Abhishek_Ajmera]

Is there some way to see the whole error message other then the screenshot i sent above?

screenshot of the jql

And this is the screenshot of the edit issue after lookup

[Stefan Salzl]

I meant the screenshot but clear readable?

To further analyse: could you please add 2 logging actions to your rule like the following screenshot, trigger the rule and send a screenshot of the audit rule?

Best
Stefan

[Stefan Salzl]

Hi @Abhishek_Ajmera 

I could reproduce the behaviour. On my side this happens if the epic names contains of a quotation mark (").

[Abhishek_Ajmera]

Thanks @Stefan Salzl I think my error is different, it says 

"Custom Smart Value JQL Search: "("Epic Link" = "Epic Name: 1") AND (project in (19904))" - The option 'Epic Name: 1' for field 'Epic Link' does not exist." 

Also I double verified that neither the epic name nor the title contains any quotes. It does have a colon (:) in the name though.

[Stefan Salzl]

I checked a few special characters but not the colon. 

In case your question is resolved please consider to mark the answer as accepted to mark the question as resolved and help other users who are in need of this information an looking for solution.

[Abhishek_Ajmera]

@Stefan Salzl i didn't mean that it was causing it, I removed that colon also from both the epic name and title but it is still the same error.

[Stefan Salzl]

Hi @Abhishek_Ajmera ,

for further analyse could you please configure/add „logging action“ as described in one of the previous replies?

And please if possible a screenshot of both the userStory and the expected epic?

Does this happen with other epics too or only with a specific one?

Best
Stefan

[Abhishek_Ajmera]

Hi,
please find the screenshots attached.

[Stefan Salzl]

Please also add thr screenshot of those issues from previous post (story and epic)

[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."

[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

[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.

[David Roy Morin]

Any update on this I have the same issue