Dynamic fields based on external data

[Ganthe_ Yash]

Our company uses multiple SaaS applications. There is one SaaS that maintains a list of all projects the company is currently working on. There is another SaaS that has a list of all servers hosted in the company. There are many more such SaaS applications. They all either expose an API or provide an export of certain key data maintained in the application.

When creating tickets in Jira, we would like some fields to have a dropdown with the options coming from data obtained from these SaaS applications. For example, when creating a ticket related to software upgrade, the user should be able to choose from among the server names obtained from the SaaS application.

In short, we would like to create fields that are integrated with the SaaS applications. What is the best way to do this?

[Derek Fields _RightStar_]

@Ganthe_ Yash Welcome to the community. You may get answers from some app providers that target specific SaaS applications. I will leave those answers to them.

Are you using Jira or Jira Service Management (or both)? If you are using Jira Service Management, then I would make use of the Assets feature as a place to store the data from the SaaS application. You would create a script or automation that would query the SaaS application on a regular basis to update the Assets objects with the current list. 

Using Assets, you can create a field that will show the most recent list of objects from the SaaS application.

If you don't have JSM, which you need for Assets, it might be worth licensing it at the lowest level just to get access to the Assets feature. Once you have it, you can use it in Jira projects as well.

[Ganthe_ Yash]

We have JSM and Assets. We have used Assets in JSM dropdown fields. But we do not know whether they can be used in Jira fields. Is there any documentation that indicates it can be?