I want to be able to mark some issues as a Regression and Reopened. Looking at custom fields, I couldn't find any boolean fields to add. Any idea how to do that? * Regression: should be true/false or true/none field (boolean). * Reopened: should be a true/false or true/none field (boolean), that can't be set or changed by a user - it changes be a rule (when transitioning from Resolved to Todo) By now, it works if I use text fields, but since it's not a boolean, the searches become complicated. How can I use a boolean field as a custom field? Is there any other option for that?

nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How to mark an issue as a Regression Bug or Reopened Issue

Uri_q848uv

I want to be able to mark some issues as a Regression and Reopened. Looking at custom fields, I couldn't find any boolean fields to add. Any idea how to do that?

Regression: should be true/false or true/none field (boolean).
Reopened: should be a true/false or true/none field (boolean), that can't be set or changed by a user - it changes be a rule (when transitioning from Resolved to Todo)

By now, it works if I use text fields, but since it's not a boolean, the searches become complicated.

How can I use a boolean field as a custom field? Is there any other option for that?

Accepted answers

Stevan Mandić

@Uri you can create select list (single option) custom fields and define options in custom field configuration (context & default value)

Option 1: True

Option 2: False

All comments

Stevan Mandić

@Uri you can create select list (single option) custom fields and define options in custom field configuration (context & default value)

Option 1: True

Option 2: False

Nathan Phillips_kcvugf

Hello @Uri

I agree with @Stevan Mandić, a Select List custom field would be a great option to meet your needs.

More information on how to configure custom fields can be found here.

Thanks!

Uri_q848uv

Thank you @Stevan Mandić and @Nathan Phillips .
I was looking something like a boolean. The problem with strings is when doing a search, because not all the 'not true' are marked as 'false', because most of them can have this field empty

Stevan Mandić

@Uri

You can solve that problem in 3 ways

1. If you have true and false options set, you can treat "empty" as False

So your JQL for false state will be (field=False or field is empty)

2. Set default value for the field (for instance: False) and you will not have issues with empty field.

3. Instead of using two options, use only one option - True.

Then you will have 2 states of the field: True & empty ( non-empty & empty)

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

custom-field

jira

cloud

jira-cloud