We have 1 project with 2 boards and the Acceptance criteria is mandatory in the issue.
When creating the ticket in the backlog it is too much work for one board to have it mandatory. So, I'm looking at an option to make it optional in one board if it is possible.
Hi @Krish.loku ,
It is not possible to make fields mandatory according to the boards. Instead, you can consider creating a new project or using a different issue type within the same project that requires the acceptance criteria field.
Thanks.
Thanks for the reply @GNarsimhagowda - Empyra . Is it possible to have a default value in the acceptance criteria field?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
It is indeed possible to include a default value in the acceptance criteria field. However, it is important to note that you cannot have different default values for different boards in the same project.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks @GNarsimhagowda - Empyra , We have created a default value and by pass the need to fill it all the time. We used default as "N/A"
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Krish,
Boards are just views of the data, so they have no impact on being able to trigger things or prevent them. Fields are attached to Projects and/or Issue Types. So unless the boards use different Issue Types, then you will not be able to do that. If they do use different issues types, then create a Field Configuration for each Issue Type in the Field Configuration Scheme for the project. Then update one of them to make the Acceptance Criteria field Required.
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.
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.