Dynamic conditional custom fields

[Dominik Kaźmierski]

Hello Atlassian Community!

Is there any way to create a dynamic, conditional custom field that works on the issue creation screen, the issue view/edit screen and in the customer portal?

It can be done through a Marketplace app (preferably free for all users 😉), a Forge app, or any other available solution.

What’s my use case?

I have two custom fields: Custom Field A and Custom Field B.

• Custom Field A is a list of application names.

• When a user selects an application from Custom Field A, I would like Custom Field B to display a multi-select list of issues or requests related to the selected app.

Custom Field B can either:

• be a single field containing all possible options, with options shown conditionally based on Custom Field A's value,
  or

• be multiple fields, hidden or shown depending on the selected value in Custom Field A.

Example:

1. User selects “MS Teams App” from Custom Field A.

2. Immediately below, Custom Field B displays a multi-select list with options like:

   • “Invalid status on Teams”

   • “Can't make a call on MS Teams”

   • etc.

Unfortunately, Forms (Pro Forma) aren't a good fit in this case, because they require agents to create tickets via the customer portal and add extra layers to the issue view, making it less clear and harder to manage.

Thanks in advance for your help and suggestions!

[Josh · Accepted solution]

Hi @Dominik Kaźmierski .

Have you looked at JSM Assets? They can be really powerful for working around a lot of the Forms limitations and you can even use it to have multiple layers of cascading fields. For example:

1. Option A
   1. (filtered by A) Option B
      1. (filtered by B) Option C

Asset & Configuration Management with Jira | Atlassian

A Guide to Asset & Config Management with JSM | Atlassian

[Dominik Kaźmierski]

Hello @Josh ! Thank You for your answer. It seems that this would do the trick, thanks!

[Olha Yevdokymova_SaaSJet]

Hi @Dominik Kaźmierski 

Smart Forms for Jira can help you achieve some kind of dynamic, conditional behavior, especially when it comes to customer-facing submissions and reducing field clutter in the issue view.

marketplace.atlassian.com

Smart Forms supports When/Then logic, so you can show or hide fields based on a previous selection.

Example:
If a user selects "MS Teams App" from a dropdown (Field A), then Smart Forms can show a related multi-select (Field B) with options like:

• “Invalid status on Teams”

• “Can’t make a call”

• “Audio not working”

This keeps forms clean, relevant, and easy to complete.

---

🔄 2. Pre-Filled Options from Jira Data

You can pre-fill Smart Form fields (like dropdowns or checkboxes) using values pulled from Jira custom fields—which means Field B can be automatically populated with app-specific issues or request types.

---

🌐 3. Works Without Adding Agents

Unlike some other solutions, you don’t need to provision Smart Forms users as Jira agents.

• Forms can be used by internal users, customers, or shared via a public link

• Responses can create new issues or update existing ones

• No extra cost or complexity from licensing more agents

---

🧩 4. Flexible Placement: Non-Jira public access + Customer Portal + Internal Use

• Attach forms to Customer Portal request types, so external users can submit dynamic requests

• Share public forms externally via link—great for feedback or intake use cases

• You can also open and fill Smart Forms within the issue view, without navigating to the portal