My goal is to make the 'Affects Version' field required when users create a new issue of type Bug for a specific project.
The problem is that a field may be made required, but it will affect all screens which utilize the field. The Affects Version field is currently used on multiple screens across multiple projects. Not all of the screens are related to the bug issue type.
What is the best approach to accomplish this task?
I cannot just make the Affected Version field required on the Field Configuration screen because then it would be required on non-bug related screens.
Thank-you!
@Dean Del Ponte Did you manage to resolve this issue as I am facing the same problem. I have mapped with the field "Affects Version" only my Bug Screen but it is aksing it for Story for example even when the field is not mapped in its screen? Thanks in advance!
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.