Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

I am unable to find "Create lookup table" action in Automation Rule

Shruti Shrivastava December 11, 2023

I am unable to find "Create lookup table" action in Automation Rule

I see an option of creating loopup issues but there is no action called - "Create lookup table"

I have to use the new Lookup Table to store the results from multiple queries and send them in an email report.

1 answer

1 accepted

1 vote
Answer accepted
Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
December 11, 2023

Hi @Shruti Shrivastava -- Welcome to the Atlassian Community

Which version of Jira are you using: Cloud, Server, or Data Center?

The lookup table action is only available with the Cloud version at this time.

Kind regards,
Bill

Shruti Shrivastava December 12, 2023

@Bill Sheboy Thank you Bill for replying back.

It is Data center.

Since it is not cloud, is there a way we can store list of issues coming from multiple queries and collate them while sending through an email?

Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
December 12, 2023

Based on what you described, there is no way to do exactly that with the Server or Data Center versions.

You could get the results of multiple queries but you cannot collate them.  You could get some results and list them individually as groupings.  (The reason collating is not possible is automation rule list iterators cannot see outside the scope of the list, such as for filtering, merging, etc.)

With Data Center, I believe you could have up to 3 result sets in an email:

  1. Both Server and Data Center have the bulk-handling feature for issues in a branch (or scheduled trigger).  And depending on your rule structure, this could use the {{issues}} smart value, as described here: https://confluence.atlassian.com/automation/run-a-rule-against-issues-in-bulk-993924653.html
  2. Data Center has the Lookup Issues action.  That would allow accessing one list of issues for a JQL query, as described here: https://confluence.atlassian.com/automation/jira-automation-actions-993924834.html#Jiraautomationactions-lookup-issuesLookupissues
  3. Both Server and Data Center have the Send Web Request action.  That could be used to call the issue search REST API function to gather and list the issues.  Please look here to learn more about that one: https://confluence.atlassian.com/automation/jira-automation-actions-993924834.html#Jiraautomationactions-sendwebrequestSendoutgoingwebrequest

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events