I'm building an automation rule that performs a JQL query based on a schedule and sends a Slack message using the result of the query. At the moment, I am using the lookup issues action to perform the JQL query.
However, based on the lookup issues description here https://support.atlassian.com/jira-software-cloud/docs/automation-actions/, it seems like we are not able to access custom fields?
I have tried
{{#lookupIssues}} {{Custom Field}} {{/}}
(including other variants as suggested by other users such as using "Custom Field", customfield_id, field.Custom Field, etc) to no avail.
On the other hand, when I checked the "Run a JQL search and execute actions for each issue in the query." checkbox in the schedule trigger and perform the JQL query there,
{{issue.Custom Field}}
works as expected. But the problem now is a Slack message would be sent for each issue.
This is not ideal because I want to format my Slack message as follows:
Some text here:
{{#lookupIssues}} {{Custom Field}} {{/}}
some more text here
which would not be possible if one Slack message is sent per issue. Is there an alternative that can solve this?
Hi @Nuraini Aguse ,
I'm new to this lookup feature, but it seems that custom field are not available in the lookup action indeed.
What you can do is lookup issue searching by your condition eg:
JQL : customfield = A and status = Open
and your action will have all issue with that customfield A , not ideal but still possible to aggregate the information.
I'm afraid i didn't help you with your question, let's see if someone from Automation team can answer it :)
Also I'm sharing this great document that describe Slack integration, maybe it can be helpful for you:
Thank you for your response. Unfortunately the Custom Field can have multiple possibilities and it's impossible to enumerate all of them.
Would love to have the ability to access the Custom Field from lookupIssues because there's so many use cases for it :)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Would love to have the ability to access the Custom Field from lookupIssues because there's so many use cases for it :)
Big +1
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.
For Reference to others that are looking for this information
Adding custom fields to Lookupissues does now work for cloud, communicated here:
https://community.atlassian.com/t5/Automation-articles/New-lookup-issues-fields/ba-p/1873978
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Krister,
What are the limitations in the Jira Data Center & its custom fields?
What type of Custom Fields do the lookup issues work to get the data of those custom fields displayed through email notification?
Can you please help me with this?
Regards,
Yash
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.