The function works correctly in the filters section:
but when I run the same JQL in the automation test it shows "0 issues found":
Could someone help me find out where the error is?
Thanks!
What is the scope of your rule: project, global, or multiple-projects?
And if it is project scope, in which project is your rule stored?
I hypothesize your rule is project-scope and not in the PRIUR project. Thus the rule only has visibility to issues in the rule's project, and so the JQL returns no issues when you try to validate it.
When a rule needs to access issues in all (or multiple projects), create the rule at a global scope and adjust the rule details accordingly. Only a Jira Site Admin (or Org Admin) can create such rules, as they can have a large impact on the site. Please discuss this with your admin for more details.
Kind regards,
Bill
Hi @Bill Sheboy , thanks for the reply! It is multiple-projects
I adjusted the configuration adding the 2 projects that are affected by the automation and JQL finds the correct issue.
But when replacing the issue id in the JQL with the smartvalue {{issuekey}} it stopped working and shows this error:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for that audit log image, as it shows the smart value added to the JQL for the linkedIssues() function is null / empty.
Would you please show images of your entire rule and an image of the branch details with the smart value in that function? That context may help explain what is happening.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Bill Sheboy of course!
The objective of automation is to detect modifications in the issue of a project and synchronize it with the issue of another project (both issues are linked issues)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
In your branch JQL, it has this:
issue IN linkedIssues({{issuekey}})
I believe it should instead be this:
issue IN linkedIssues( {{issue.key}} )
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.