Auto-fill fields based on multiple inputs.

[NSEU DevOps]

I am creating an issue type called "New Project" for our SYS/SW/Test teams to request new project setups.

As part of this new ticket type there are a number of requirements that I need to define (and then develop myself).

One of which is to allow for the key to be automatically defined based on a set of inputs.

The requirement takes the following inputs to generate the key as an output

Project ID - Text Field

Category - Drop down list with the following options

• RFX
• Series
• Derivative
• Change Request
• Maintenance
• Test
• Software

Customer Name - already defined drop down list.

• Porsche
• Ferrari
• BMW
• Mercedes
• JLR

For example: If our customer was Ferrari and the project was a test project. The key generated by Jira would be "SFR0001T"

S = assigned because its a series product

FR = Customer

0001 = Project with this customer

T = The Category (in this instance a Test project). 

I would also like some way that the 0001 increases. I appreciate this may require a custom script or an extra DB.

Thanks for reading.

Alex

[Mark Segall · Accepted solution]

Hi @NSEU DevOps - Unfortunately, there's no way you're going to be able to do this natively.  You ultimately need some type of database to store the friendly name/code combos you're referencing. The Assets (formerly Insight) feature may be able to help with this.

Additionally "Key" is a Jira-specific locked down field that you cannot manipulate.  You would need a custom field that would contain your desired detail.

There may also be some marketplace options out there, but at the heart of this requirement, you'll need something that provides the database capability to map the friendly name to a code.

[NSEU DevOps]

Hi @Mark Segall

I've worked out a theory to get round this problem. Initially we do not want to change the way the key field works. Rather create a custom field that will take data from other custom fields to produce a "Suggested Key" field.

My description was quite confusing. I apologise. But I believe I have a way to solve this using Jira Automation.

Thanks for your time.