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

Default value not showing for a custom field but displaying unexpected other value instead.

Need some helps here!



I have created a custom field named "Services" which include options of my app features. It is a mandatory field, required select at least one option before transitioning incident ticket to "complete" status.

Problem spotted:

I have set this custom field to be appeared in Screen during transition ticket from "Work In Progress" to "Complete" status, however i notice that every time i transit a ticket, this field not showing "None" by default but "Other" option instead which is not my expectation.




I come to check this custom field configuration, no 'Other' option is set as default one.



Business Impact:

Due to this issue, i have detected that 'Other' option of Services field have been increasingly selected by default (Not my expectation, repeated) rather real choices that really match for incident scenario. This causes frustration when i have to run the monthly report as the collected data has been compromised.


It's kind of weird issue.

Appreciated all commented advice here.


4 answers

Dear @John Funk @Nic Brough -Adaptavist- @Fabio Racobaldo _Herzum_ @Mahesh Shinde 


I have investigated and finally found the root cause.

Someone in my team has added "Services" field as a hidden one in my team "Request Form" and set "Other" as a default value, when customers submit the form, the Service's "Other" value is secretly saved and represent again on the screen transition.


Then i reproduced the case by setting "Service" field to show up on "Issue View", and raised a dummy ticket through the following form. "Other" value is displayed as well.


To fix the issue, i remove the hidden field "Services" and save this Request Form, the 2nd dummy ticket created and it showed that no "Other" value was represented but "None" instead.

Root Cause.png

Thank you for guiding me on this issue guys.




0 votes

Hi @Somnuek Hongcharoenkul ,

if you define a field as mandatory, None option will not appear. As workaround you can add your own option ("None" or something similar) and make it as default value.

Hope this helps,


0 votes

There's a couple of layers to this, and some of it means that I want to explain a little bit of Jira-speak to frame it a bit.

You say " It is a mandatory field, required select at least one option before transitioning incident ticket to "complete" status."

In Jira, a mandatory field is one that is mandatory from the start of its life.  It is a flag in the field configuration which means that you can't even create an issue without selecting (or defaulting) a value.

Making a field mandatory in a workflow (i.e. you can leave it empty until you try to close the issue for example) is done with validators, not the mandatory flag.

So this begs the question of how you have made the field mandatory, and might explain what you are seeing:

If you have done it in field configuration, then you are getting "other" entered into the field when the issue is created, because you can't create an issue without filling in mandatory fields.  People are selecting other when they're not sure.  Your default of "none" won't go through.

A default value only applies to the create process, you don't default data on to issues once they've been created.

So, I think what you are seeing is actually correct behaviour for what you've set up.  But what you actually want to do is make the field optional, still default it to "none" and then add a validator to check that it gets filled before they complete the issue.

John Funk Community Leader Jul 16, 2022

@Somnuek Hongcharoenkul  - are you able to answer Nic’s question? Can you look at an existing issue that has been created but is not done yet and does it have a value of Other for that field already?

Hi @Somnuek Hongcharoenkul :

Can you check if there is condition, validator or post-function configured for this field in workflow transition or is there any automation configure using third party app?

Also try to do project indexing for this project.


Mahesh Shinde

I have rechecked and no mentioned extra step added to this field, including automation change too.

May i request a source of doing project indexing? 

You can't re-index projects on Cloud, it handles all of that for you automatically.

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events