can a field for an issue type, let say a bug, be required in one project and optional in another project?
Hi @jeroen_wilmes,
Yes, that is possible. You can either use a different field configuration in different projects or - as an alternative - use different workflows with specific required field validation in your different projects.
Hope this helps!
Hi Walter,
For now we made specific field configuration schemes and that works. Meanwhile I'm still interested to learn the alternative you mentioned, although the link is not working (anymore). Can you have a look at the link.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Many thanks
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.