Hi,
I'm using an Automation rule to send an email with a list of issues (as described in this article).
I'm having problems with some smart fields.
This
{{#lookupIssues}}{{key}}, {{/}}
provides a list of issue keys, as expected.
But this
{{#lookupIssues}}{{priority.name}}, {{/}}
provides a list of blank values (“, , , , , , , , ,”). The same thing happens with {{priority.iconUrl}}, {{duedate}} and {{duedate.jiraDate}}.
Does anyone know what the problem may be? I’m using Jira Cloud.
Thanks,
José
Looking at this documentation, Priority is not one of the fields supported for lookupIssues:
https://support.atlassian.com/jira-software-cloud/docs/automation-actions/
I checked the public suggestion backlogs for JIRA Cloud and Code Barrel, but I could not find any open items to add this field.
Best regards,
Bill
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
+1 for this feature—would love if lookup issues could support priority!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Owen Scott -- Welcome to the Atlassian Community!
Unfortunately, my suggestion to add the other fields to Lookup Issues got moved to the dreaded "future consideration" status: https://jira.atlassian.com/browse/JRACLOUD-75018
You may still vote for it/watch it if you wish.
Best regards,
Bill
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
the dreaded "future consideration"
Haha, thanks for getting back to me! I added my +1 to your feature request.
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.