nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How to make a field mandatory for a specific transition and an issue type

Chethana Hashani

Hi All,

I need to make "affects version" field mandatory only for bugs when they are created. Could you please guide me on this

Cheers,

Hansi

Accepted answers

Yogesh Mude_u145qk

HI @Chethana Hashani

You can do this using field configuration but it will make the affects version field mandatory only on the create a screen.

If you want to do this for a specific transition or workflow transition screen then you need to use Jira Suite utility or Behaviour script runner add-on.

All comments

Tushar_y7owr9

Hi Hansi,

Create field configuration scheme for the "Bug" issue type, and then make "Affect/s Version" field as required within that field configuration scheme.

~Tushar

Yogesh Mude_u145qk

HI @Chethana Hashani

You can do this using field configuration but it will make the affects version field mandatory only on the create a screen.

If you want to do this for a specific transition or workflow transition screen then you need to use Jira Suite utility or Behaviour script runner add-on.

Chethana Hashani

Hi Tushar,

Initially I hadn't anything in my field configuration schema screen and it was like this

SCR 1.png then as you said, I created my very first field configuration schema as "Bug Configuration Schema". But once I created it and saved it, I got a screen like below with a schema called "Default field configuration" instead of "Bug Configuration Schema". It doesn't show me the schema which was created by myself. I am bit confused now. can you please guide me on this as well (I am new to Jira )

scr 2.png

Chethana Hashani

Hi Yogesh,

What I exactly need to do is making affect versions field mandatory, only when creating a bug. So I guess field configuration could support me. Thanks a ton for your information

Cheers,

Hansi

Tushar_y7owr9

Click on "Associate an issue type with a.." and map the newly created bug field configuration with Bug issue type.

~Tushar

Chethana Hashani

Hi Tushar,

I clicked on "Associate an issue type with a.." and map mapped new bug field configuration with bug issue type. Please find the steps I followed,

step 1:

Scr 3.png So then I got this screen,

Scr 4.png After that as you said I made "affects version" mandatory in default field configuration as in the below figure:

scr 5.png But then, when it applies to all issue types (not only for bugs). When i try to create a task also, it asks for an affect version

scr 5.png For sure I know I have missed a step. please guide me on this

Cheers,

Hansi

Yogesh Mude_u145qk

HI @Chethana Hashani

As mentioned by @Tushar, please make a copy of default field configuration and the respective field configuration scheme as well.

Rename both (default field configuration & field configuration scheme), associate the newly created field configuration to Bug issue type and respective field configuration scheme.

Apply the field configuration scheme to the respective project and then make the Affects Version field mandatory/required.

Chethana Hashani

Hi Yogesh,

Oh my bad I haven't linked it to the relevant project. Now it is working. Thanks a ton and sorry for bothering that much

Cheers,

Hansi

Marc Jason Mutuc

Recommended way is doing this via Field Configuration.

1. Create the Bug Field Configuration and make Affect Version/s "required"

2. Add it to your project's Field Configuration Scheme and make sure to have it associated with the Issue Type "Bug"

3. Just to check, your Field Configuration Scheme should have two Field Configurations. One for Bug and another for everything else.