Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Is this how Checkbox and Radio Button fields are supposed to work in Jira?


We are using Jira 8.13.0 Server.

I have wanted to use checkbox and radio button custom fields in JIRA but they do not behave in a way I am used to.  The only values that are visible are those that have been selected. A user cannot see the checkbox or radio button selection unless they go into the edit screen. Is this normal behavior in Jira?

I expected all values to be visible outside of an edit screen or edit pane.

What is seen after selecting field values:

2021-01-22_14-01-58_Image 001.jpg

Selecting values from the Radio Button Custom field:

2021-01-22_14-01-07_Image 001.jpg


Selecting values from the Checkbox custom field:

2021-01-22_14-01-44_Image 001.jpg

If the Checkbox or Radio Button selections are not visible there's not much point in having these two custom field types, is there?  I could just use a Select List Custom Field because it appears the Checkbox and Radio Button fields are behaving exactly like a Select list except instead of making a selection by clicking on the item I'm using a checkbox or button to make the selections.

1 answer

1 accepted

2 votes
Answer accepted
Mike Rathwell
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Jan 22, 2021

Hi @James Malgieri 

I shall try to not "rant" on this one as it is a UI approach in Jira that has long been an annoyance for me. The approach is that fields without values are not displayed on the screen. Once they DO have a value, you can see and edit them.

To my tiny mind, especially for fields such as you cite, they should be "on top" all the time and not only when they first get information in them. It would be nice if the ability to display empty fields were configurable.

The only way I have gotten fields to display in your scenario is often not the best situation where one would set a default value in them so they are onscreen. The danger there is that, if you want a real and true value put in from time to time, often, if it is on the screen with a default value, the users don't. Worse, you can't check that a value was put in consistently in the workflow.

So... short answer, they do behave differently than one might think and the only way to have them on screen by default is set a default value.

Mike, thanks for your input.

It's doubly confusing when you add Confluence into the mix. At least there you can create a checklist - which is nothing like the Jira checkbox custom field and ends up confusing customers because they see Jira and Confluence as Atlassian software so of course they look and behave the same - which they don't.

To me, and a lot of other people, a checkbox/radioButton list should be a list of displayed values that are selectable by the checkbox or radio button - indicated to the user by an "x" in the checkbox or "dot" in the radio button.  Now I'm trying not to rant.

Oh well.

btw: A few years ago we had a user who wanted to "see all of the fields" whether or not they had any data in them.  We tried using a single dot/period as the default value - which did work but it looked really ugly.

Like # people like this

I totally agree.  The radio button and checklist are no different than a single list dropdown.  

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events