Adding conditional fields in Create and Edit Issue Screens (Jira Software)

[Adi Nitisor]

Hello, In Jira Software I have a set of multi-select dropdown fields in a 3-tier hierarchy: This hierarchy will be heavily populated with options and I want to only reveal the relevant fields to each task owner so that the Create / Edit issue screens don't become filled with unnecessary fields. These would be multi-select dropdowns, so task owners could pick several options.
I noticed that I can attach forms that offer this conditional functionality, but they seem to only work for Creating issues. If a task owner needs to Edit Issue, he would revert to the regular screens that don't seem to provide this functionality.
I know that Jira Service Management offers this functionality but I would try to stay with Jira Software for other features that serve well for our workflow.

Is there a way to bring this functionality, through forms or regular Jira task screens, so that it is available both when Creating and Editing Issues? If not natively, then through add-ons maybe?

Below is a very simplified structure, to better illustrate what is my intention:

Dropdown
Option 1 (first tier)
   -> Option 1A (second tier)
             -> 1Aa (third tier)
             -> 1Ab 
             -> 1Ac 

   -> Option 1B (second tier)
             -> 1Ba (third tier)
             -> 1Bb
             -> 1Bc

Option 2 (first tier)
   -> Option 2A (second tier)
             -> 2Aa (third tier)
             -> 2Ab
             -> 2Ac

   -> Option 2B (second tier)
             -> 2Ba (third tier)
             -> 2Bb
             -> 2Bc

The task owner could pick from the above any number of options, but if he only wants to pick options 2Bb and 2Bc, he would only see the first tier dropdown, then when he picks Option 2, I would reveal a new dropdown with options 2A and 2B, and when he picks 2B I would only reveal that dropdown with 2Ba 2Bb 2Bc.

[Maciej Dudziak _Forgappify_]

Hi @Adi Nitisor 

In Jira Software, this is possible using the UI Modifications API, which supports Create Issue, Issue View, and, more recently, Transition View. There are several apps on the marketplace that leverage this API. 

I am from Forgappify and we developed a Show field rule, which is part of Field Rules - UI Modifications for Jira app. With the Show Field rule, you can conditionally reveal fields based on selections made in other fields or user preconditions such as project roles, groups, and individuals. Additionally, the Hide Field Options rule allows you to limit the number of displayed options in a custom field dropdown.

Depending on the semantics of your use case, I would populate multiple custom fields with options and use the Show Field rules to dynamically reveal the relevant ones. If it makes sense to keep some options within a single field, I would do so and utilize the Hide Field Options rule to display only the options relevant to the selected context.

I hope you can give it a try.

Cheers

[Atlass Monster]

I no have idea, probably there is a paid way but i'm too cheap.

If I were on your place I will set up one separate project like ITSM, just something to hold forms.

If possible, use the options for conditional logic to create your desired mess of option levels.

Link: https://confluence.atlassian.com/jirakb/using-conditional-logic-with-forms-1167693620.html

You can set up the Form to be open for edit:

" But how this can help me crazy furry beast? "  You can set up an Automation to copy the values from the request in the other project to the values in the Jira fields. I think it is possible to link the issues together so it's all tightly together.  It won't be pretty and will be time consuming at first to set up, but it free mate...