Can I automatically populate a field based on the value in another field?

[Marcus Ladd]

We are using Jira Cloud to manage our software tickets. When creating bug tickets for our developers, it is helpful to include both the customer name and unique ID of the customer's site. However, while I may know the name of the customer simply by looking at the site, I won't necessarily know the unique ID without referencing our internal documentation.

I would like to create two custom fields that are associated with one another, such that if I select the customer name from a pre-populated list when creating the ticket, the unique ID field will be automatically populated based a second pre-populated list.

For example, I have a table:

Customer | Site ID

John's Coffee Shop | abc123

Bill's Auto Shop | def456

Tom's Flowers | ghi789

I would like to create custom fields called "Customer" and "Site ID". When I select "John's Coffee Shop" from the available list of values for "Customer", I want to see "Site ID" populated with "abc123".

[Murat Seven · Accepted solution]

Hi @Marcus Ladd and welcome to the Atlassian Community!

You can automate using the Create Lookup Table automation action.

example for your case;

If the answer helps, please accept the answer.

Best regards,

Murat Seven

[Marcus Ladd]

This is perfect, thank you!

[Murat Seven]

You're very welcome! I'm glad I could help @Marcus Ladd :) 

[Trudy Claspill · Accepted solution]

Hello @Marcus Ladd 

Welcome to the Atlassian community.

How many customers do you have, that you would need to map to sites?

Is the place where that is currently documented something that could be referenced through a REST API call that you could use to get the Site associated to a specific Customer?

If so then you could use the Send Web Request action in an Automation Rule to execute that call to get the Site, and then rule could update the issue.

Do you use just the Jira product or do you also use the Jira Service Management project?

If you use the JSM product also, then you might want to consider documenting the Customers and Sites as Assets, which you could then reference through Automation Rules to look up a customer and get their associated site?

These solution and @Murat Seven 's suggestion would be updating the Site field only after the issue is created.

If you want to update the Site field dynamically while the user is still in the Create Issue dialog, that would require a third party app.

[Marcus Ladd]

Thank you Trudy! We are using just the Jira product and the number of customers is large enough that it would be difficult for me to keep track on my own. I am going to try Murat's suggestion since I don't need the field updated while still in the Create Issue dialog.

[Trudy Claspill]

Hello @Marcus Ladd 

Be advised that a Lookup Table is limited to 200 pairs. If you have more than 200 customers, you will have to create multiple Lookup Tables in your rule and execute multiple actions to check each one to see which one the customer is in.