Can I create a Jira field with associated sub-fields?

[Kevin Goohs]

A portal form is collecting multiple field information.  Ultimately, this leads to a released version that will be available for deployment.

When a deployment request is made, I would like 4 other fields automatically added to the deployment request ticket based on the release version selected.  

[Trudy Claspill]

Hello @Kevin Goohs 

Welcome to the Atlassian community.

When you say you want 4 other fields added, do you mean made visible to the person filling out the deployment request so that they can select values for those additional fields?

Or do you mean you want the 4 fields to be populated automatically with data after the request is created?

If you want the fields populated with data that can be done with an Automation Rule.

If you want the fields to be displayed conditionally to the person completing the request that requires a different solution which depends on the type of Space this concerns - Software, Service, or Business. And if it is Service, it also depends on if you want the fields shown to a user completing the request through the customer portal, or an internal user completing the request through the internal Jira/JSM UI.

[Kevin Goohs]

Hello @Trudy Claspill 

Thank you!

I want the 4 fields to be populated automatically.

[Trudy Claspill]

Then you should be able to do that with an Automation Rule.

Are you familiar with Automation Rule functionality?

https://support.atlassian.com/cloud-automation/docs/jira-cloud-automation/

There are several courses available as free, on-demand training through the Learning link at the top of the community pages. Here is a search to get you started.

https://community.atlassian.com/learning/catalog?product=Jira%2CJira+Service+Management&search=automation

If you are not familiar with the features you may want to reduce the search to items at the Beginner level.

[Kevin Goohs]

I am familiar with Jira Automation and use it extensively.  I will follow-up w/in the Learning link.  Thank you

[Trudy Claspill]

Let us know if you come up with more questions.

There are two basic scenarios to consider for automation:

1. When the deployment request is created and release version is provided
2. When the release version is changed in an existing deployment request

Other things to consider:

1. Does the field you are using for release version ever have multiple values?
2. What do you want to do with the dependent fields if the release version is cleared?
3. If "release version" is a reference to a Version in the project, do changes need to be made to the 4 fields if data within that Version is changed?
4. Is "release version" set manually or through automated processes (automation rules, workflows, integrations)? That could impact your rule structure.
5. Is it possible to change a work item type from another type to a deployment request, or from a deployment request to another work item type? Should that have any impact on the 4 fields?