How to make the 'component/s' field required only for a certain issue type or screen?

[Lior Pesoa]

Hi,

I would like the default 'Component/s' field to be required only for a certain issue type or a specific screen.

Is that possible?

Thanks!

[Tarun Sapra]

Please add a specific "Field configuration" for the that issueTYpe and make the components field mandatory on that field Configuration. Once you make it mandatory it would appear on the screen with a red Astrix which means mandatory. The solution by @Elifcan Cakmak is also possible but it in that case user would see the error after he has pressed the create button and then the error would come that "component" is mandatory.

[Tarun Sapra]

Please see here - https://confluence.atlassian.com/adminjiraserver071/specifying-field-behavior-802592555.html

"whether the field is required (i.e. the field will be validated to ensure it has been given a value) or optional"

And you have can have a different field configuration for different issueTypes in the same field configuration.

https://confluence.atlassian.com/jira064/configuring-fields-and-screens-720412098.html

[Nic Brough -Adaptavist-]

To be clear on that validation option - you're not making it "mandatory on a screen", you're making it "mandatory to go through a transition".  It's easy to set up an example where you use the same screen for an "edit" and a "transition", and the field is only mandatory on the transition.

[Lior Pesoa]

@Tarun Sapra i get what you are saying, but it doesn't work for me. can't get the 'Component/s' field to be mandatory on a specific issue type.

[Tarun Sapra]

@Lior Pesoa Can you paste your field configuration? and field configuration scheme screenshots. thanks

[Lior Pesoa]

sure @Tarun Sapra

thanks!

Snip20160816_104.pngSnip20160816_105.pngSnip20160816_106.pngSnip20160816_107.png

[Tarun Sapra]

thanks, can you also share the screenshot from the "fields" section of the project-admin section , I want to see the field configuration scheme mapping the project admin section versus the issueTypes

[Lior Pesoa]

this ?

Snip20160816_108.png

[Tarun Sapra]

Thats your problem right there, you are using the default field configuration scheme for all issueTYpes, you haven't associated the project with the "Field configuration scheme" which contains the Field configuration scheme for the issueType "Members experience"

[Lior Pesoa]

but when i change the project field configuration scheme it changes 'component/s' to be mandatory for both 'bug' and 'members experience' issue types.

i want it to be mandatory only for 'members experience' issue type

[Tarun Sapra]

Then you need to configure your field configuration scheme in such a way that the field configuration in whcih components is mandatory only applies to members issueTypes and not for bug thus different behaviour for diff. issueTypes it's easy to do - https://confluence.atlassian.com/adminjiraserver071/associating-field-behavior-with-issue-types-802592562.html

[Lior Pesoa]

finally it worked! thanks @Tarun Sapra

sometimes JIRA configurations are the hardest things to do in the world 

way too complicated UX

[Tarun Sapra]

Wow nice  , indeed UX can be confusing ( try issueType migration )

@Lior Pesoa Please accept/upvote the answer. thanks!

[Akhil V S]

Hi,

The field Component/s is a system field, therefore it cannot be configured to be made available for certain issue types you prefer. However it can be made required by going to field configuration. Its better to create a custom field component(s) and configure field context for issue types you prefer. 

[Tarun Sapra]

Creating a field which is similar sounding as that of a system field is a really bad idea. 

[Akhil V S]

In that case creating two separate field configuration for two issue types will be perfect.

[Elifcan Cakmak]

hello

you can create a different workflow for that issue type and in the workflow you can add a validator to make components field required for the transition you want.