Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

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

Chethana Hashani
Contributor
August 12, 2018

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

3 answers

1 accepted

0 votes
Answer accepted
Yogesh Mude
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
August 12, 2018

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
Contributor
August 12, 2018

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

Yogesh Mude
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
August 13, 2018

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
Contributor
August 13, 2018

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

0 votes
Marc Jason Mutuc
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
August 13, 2018

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.

0 votes
Tushar
Contributor
August 12, 2018

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

Chethana Hashani
Contributor
August 12, 2018

Hi Tushar,

 

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

SCR 1.pngthen 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 :D)

scr 2.png

Tushar
Contributor
August 12, 2018

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

 

~Tushar

Chethana Hashani
Contributor
August 12, 2018

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.pngSo then I got this screen,

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

scr 5.pngBut 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.pngFor sure I know I have missed a step. please guide me on this

 

Cheers,

Hansi

Tushar
Contributor
August 12, 2018

You made that field required in the "Default Field Configuration", which is not correct.

First thing first.

1. Make the Affect/s version field as Optional in Default Field Configuration.

2 Create separate field configuration for your requested Issue type, Eg. Bug Take copy of Default Field Configuration and name it as Bug-Field Configuration.

3 Open the Bug Field Configuration and make the required field as mandatory.

4. Now Associate that Bug Field configuration to Bug issue type within the Project Field configuration scheme.

 

Then Affect/s Version field will be appear mandatory only Bug issue type not for other issue types.

 

~Tushar

Chethana Hashani
Contributor
August 13, 2018

Hi Tushar,

1. I made "affect version" optional in "default field configuration"

SCR 1.pngSCR 2.png2. Then I took a copy of "default field configuration", renamed it as "bug field configuration" and made "affects version" mandatory there.

 

copying "default configuration field":

SCR 3.png

Renaming as "Bug Field Configuration":SCR 4.png

 

Making "affect version" field in "bug field configuration" required

SCR 51.png

Mapping it with "bug issue type":SCR 5.pngBut for the moment also, when I try to create bug, it allows me to create a bug without filling affect version nuh (it is not mandatory yet ) :/

SCR 6.png

Please help me on this

 

Cheers,

Hansi

Tushar
Contributor
August 13, 2018

Now make the affect/s version mandatory/Required  in Bug Field configuration.

Hope this will help you.

 

~Tushar

Yogesh Mude
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
August 13, 2018

HI @Chethana Hashani

You can not directly associate the bug Field configuration to project, hence please make sure that you have been associated this Bug Field Configuration to respective Field configuration scheme and then apply the field configuration scheme to the project.

Chethana Hashani
Contributor
August 13, 2018

Did but still I am allowed to create bugs without affect versions nuh. Have I missed something?

 

Cheers,

Hansi

Chethana Hashani
Contributor
August 13, 2018

Hi Tushar,

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

Tushar
Contributor
August 13, 2018

Cheers, pls vote :)

 

~Tushar

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events