Jira smart value {{lookupIssues.description}} not fetching the issue data

[flourish_x_yang]

• what version of Jira are you using: Cloud, Server, or Data Center
  

  Jira v10.3.8

  alm-jira.systems.uk.hsbc
• an image of your complete automation rule in a single image for continuity
  
• images of any relevant trigger / actions / conditions / branches
  Please check these variables in above screenshot:
  {{lookupIssues.label.name}}
  {{#lookupIssues}}{{description}}{{/}}
• an image of the audit log details showing the rule execution
  
• explain what is not working as expected and why you believe that to be the case
  

  I expected to lookup an issue ticket from another project SPCOEDM, and copy its {description, label, or components} to new ticket in project SPCOELAB, but I got null.

  Would you please guide how to resolve it?

[Trudy Claspill · Accepted solution]

Hello @flourish_x_yang 

First, based on the version number you found and the graphics in your image, you are using Jira Data Center.

On the Rule Details page, what is the Project Scope of your rule? The rule will not be able to access or find issues in any project that is not included on the Project Scope of the rule 

I suspect that the SPCOEDM project is not in the rule scope, and therefore the Lookup Issues action is not able to find the issue you specified. You will need to add that project to the rule scope. 

Only Jira Admins can't modify/create rules that have a multiple project scope, and that can be done only from Jira Admin Settings> System > Global Automation.

If you are not a Jira Admin you will need to get help from such a person.

[Arkadiusz Wroblewski · Accepted solution]

Hello @flourish_x_yang 

I think @Trudy Claspill  is very likely right about the first problem.

Your audit log already says “Lookup issues: A search during custom value definition found no issues”, and your rule is trying to look up SPCOEDM-91 from a rule triggered in SPCOELAB. On Jira Data Center, the rule scope determines which projects the rule can work across, and multi-project / all-project scope is configured from global automation. So if SPCOEDM is not in scope, or the rule actor cannot browse that project, the lookup will return nothing exactly like in your screenshot.

FYI:

- the rule scope must include both projects
- the rule actor must have Browse Projects permission in SPCOEDM
- test the JQL separately as the same user / actor if possible: key = SPCOEDM-91

After that, there is a second limitation specific to Jira Data Center automation:

lookupIssues on DC still supports only a limited set of fields. Atlassian’s KB explicitly calls out that lookupIssues does not support fields like labels and components, so those can still come back empty even after the lookup itself is fixed.

Troubleshooting Jira automation smart values that return an empty value | Automation for Jira Cloud and Data Center | Atlassian Documentation

[JIRAAUTOSERVER-877] Lookup issue action - Add support for more fields - Create and track feature requests for Atlassian products.

[flourish_x_yang]

@Arkadiusz Wroblewski @Trudy Claspill Thank you. The scope is SPCOELAB only. I tried other field like {{lookupIssues.reporter.displayName}} , it's also null. 

I will check if our JIRA admin can extend the scope.