Forums

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

Based on a value in a Jira issue, refer to a table to pull the rest of the information

Samantha Concepcion
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
August 21, 2025

Hello,

We use our Jira to track all the work items that we have to do across multiple projects, and I know we can create look up tables in automations but I don't want to repeat that for every automation we have, and have duplicate data copied. My hope is to create a table somewhere (somewhere in Jira? Confluence?) with columns like:
Project Type | Project Name | Project Lead | Project Sub Lead | Project ID
       1               Test_A                  J Doe                    J Smith          123

       1               Test_B                  J Smith                  A Name         456

       2               Test_C                  A Name                J Doe             999

And then depending on the value chosen in the Jira issue (ie. Project Name), it goes to this table, and populates fields like project lead and project id on the ticket itself. Is there a way to do that?

Use Case:
In Jira system project, a user creates a work item called Deliverable. They select Test A as their project name. A field called Project Lead will need to be populated so that the developer knows who to contact for any questions. 

Instead of this needing to be manually selected by whoever is creating the ticket (not necessarily the project lead), would want Jira to be able to refer to this table, and based on Project Name pull the applicable information.

Thank you!

2 answers

0 votes
Mikael Sandberg
Community Champion
August 21, 2025

Hi @Samantha Concepcion

Welcome to Atlassian Community!

Just to add to @Trudy Claspill answer, if you happen to have JSM then this can be solved by using Assets. You could then use object lookup in the automation to fill out the fields.

0 votes
Trudy Claspill
Community Champion
August 21, 2025

Hello @Samantha Concepcion 

Welcome to the Atlassian community.

Is there a reason you could not use a Global Rule so that the table is created only once?

Automation Rule tables support only a key and one value, so you would need multiple tables within the rule if you have multiple values to associate to a key (Project name).

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events