The field configuration scheme and field configuration (especially the context) are key parts in determining visibility and the field being required or not across projects and issue types.
These configurations will reflect in bulk update operations as well.
My feild configuration scheme is mapped with so many fields configuration.changing a field from "required" to "optional" will affect the other field configurations as well right?During bulk update there are only few fields that a user has to fill. How to view them and make the bulk update fields optional.?
No, your field configurations are all separate. But it sounds like you are sharing them. A change to a shared scheme will take effect everywhere the scheme is used.
It sounds like you need to split the field configurations up so you can remove some fields from the issues.
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs