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
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.
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Tushar,
Initially I hadn't anything in my field configuration schema screen and it was like this
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 :D)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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:
So then I got this screen,
After that as you said I made "affects version" mandatory in default field configuration as in the below figure:
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
For sure I know I have missed a step. please guide me on this
Cheers,
Hansi
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Tushar,
1. I made "affect version" optional in "default field configuration"
2. 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":
Renaming as "Bug Field Configuration":
Making "affect version" field in "bug field configuration" required
Mapping it with "bug issue type":But 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 ) :/
Please help me on this
Cheers,
Hansi
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Did but still I am allowed to create bugs without affect versions nuh. Have I missed something?
Cheers,
Hansi
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.