Create group of customfields (attributes) in a ticket's edit form

[Cosmin Papadopol]

I am looking forward to achieving something as follows. In a ticket I want to be able to add a list of directors, each with its own attributes:

Directors

- Name
- Passport
- Proof of address

Ideally, I want the form to allow to as many objects as needed based on the above template. Something like when clicking a (+) it prompts to fill the attributes under a new item.

E.g the screen should look something like this:

Director 1 

Name: X Y
Passport: 123
Proof of address: 123

Director 2

Name: Z C
Passport: 123
Proof of address: 123

Looking forward to using a 3rd pary app as well, but didn't manage to find anything suitable.

Thanks in advance!

[Walter Buggenhout]

Hi @Cosmin Papadopol and welcome to the Community!

You don't mention what Jira product (Jira Software, Jira Service Management, Jira Work Management) you are using, so let me answer with various options in mind ...

In Jira Software, every field you want your users to complete must exist as a separate custom field in Jira. So simply put, if you would want people to fill out maximum 5 directors with several attributes, you would need 5 custom fields for each possible director and 5 additional custom fields for every single attribute like passport, proof of address, ...

However, just from the description of your question, this feels very much like a request form. In Service Management, you have the ability to design dynamic forms where you can:

• use fields on your form that must not necessarily be linked to Jira custom fields
• use sections to dynamically hide / display data, which would you to only show the number of director fields you actually need and hide the ones that are not relevant.

Another option - again using Jira Service Management - would be to use assets, available in the JSM premium plan. Huge benefit is that they allow you to set up a very powerful integrated asset management solution for IT, infrastructure, HR, ... inside your Atlassian platform. But definitely also for your specific use case. There, the attributes would be linked to your directors - adding them to your ticket could be done by name only; if the attributes are defined in the asset database, they are immediately available without the need to fill them out separately. Adding assets (directors) to a ticket requires you to set up a custom field, which can be multiselect or multiple custom fields if you need to add each director individually.

Hope this helps!