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; } } }

Why the lookup issues finds my fixVersions but still fails ?

Raphaël NORYNBERG

Hello everyone,

So basically I'm trying to set the "Fix versions" field of many issues as the same value of their parent issue.

I guess it is possible through automation rules and the "Lookup issues" action, but I can't succeed to get it work.

I did that

But when the rule ran the first time it showed me that error :

"Custom Smart Value JQL Search: "fixVersions = Test auto raph" - Error in the JQL Query: Expecting either 'OR' or 'AND' but got 'auto'. (line 1, character 20)"
I didn't get why it found the good value ("Test auto raph") but failed anyway, I thought it was maybe the spaces so I made a second try with another release name without space, and again it did find the good value but failed after :

Custom Smart Value JQL Search: "fixVersions = test-version-sans-espace" - Field 'fixVersions' does not exist or you do not have permission to view it.

The first part of the rule doesn't seem relevant to me, but I share it just in case

If anyone knows how I can get it work please help me !

Thanks in advance,

Accepted answers

All comments

Bill Sheboy

HI @Raphaël NORYNBERG

For a question like this, please include an image of your complete rule and the audit log details showing the rule execution. Those will provide context for the community to offer better suggestions. Thanks!

Until we see those...

The Fix Versions field is a list of values, and so {{issue.fixVersions.name}} will produce a list when there are multiple values in the field. Also, as version names could have spaces or special characters, try wrapping the value in quotation marks. Finally with JQL, the field name is singular: "fixVersion".

Putting that all together, and assuming you only wanted to find the first value in the list, that could be this:

fixVersion = "{{issue.fixVersions.first.name}}"

Kind regards,
Bill

Raphaël NORYNBERG

Hi @Bill Sheboy ,

Thanks for your reply,

I have modified "fixVersions = {{issue.fixVersions.name}}" into "fixVersion = "{{issue.fixVersions.first.name}}"" but with there is no more lookup issues part in the log

So I got back the fixVersions but kept your "{{issue.fixVersions.first.name}}" and I have the same error as previously.

Please find audit log details below

The complete rule :

Thanks for your help

Raphaël NORYNBERG

With "fixVersion = "{{issue.fixVersions.name}}"", the rule ran with success except that it doesn't set the fix version field for the children (no erros in the logs)

Is this uncorrect ?

Bill Sheboy

Lookup Issues can gather zero-to-many issues, matching the JQL provided. As your rule image shows, it is trying to set the Fix Version to the key values in the lookup result, which will not work.

Please described what you are trying to accomplish, as your rule appears to have two purposes:

#1)

GIVEN an issue has linked issues
AND some of the linked issues are in the "To Be Prioritized" status
WHEN the trigger issue transitions to "To Dev"
THEN transition those linked issues to "To Dev"

#2)

GIVEN an issue has child issues
AND the issue has a value in Fix Version
WHEN the trigger issue transitions to "To Dev"
THEN copy the issue's Fix Version to the child issues

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud