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!
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.
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.
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
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.
@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.
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.
Creating a field which is similar sounding as that of a system field is a really bad idea.
In that case creating two separate field configuration for two issue types will be perfect.
It looks like you're new here. Sign in or register to get started.
