User's "Configure Fields" settings

From what we can tell (e.g. when creating an issue), the user's "configure fields" settings (e.g. customize to select which fields are or aren't displayed when creating a new issue) are stored / remembered as part of the user's account settings (we're on Jira 6.0).

Assuming the above is correct, we haven't been able to figure out what the default "configure settings" are for a new user. For example, if a user logs into Jira for the 1st time, goes to create an issue, and selects "configure settings", is "All" or "Custom" enabled, and how does Jira figure out which fields are selected in the "Custom" option by default? (Or is this somehow defined in the Screen Scheme / Field Configurations)?


3 answers

Yes, those fields should be defined in both Screen Scheme and Field configurations.

Thanks ck. (I'm still a little unclear though).

From looking back over the docs, they say (regarding creating an issue) that "Click Custom and select the fields you want to show or hide by selecting or clearing the relevant check boxes, respectively, or click All to show all fields. When you next create an issue, JIRA remembers your last choice of selected fields."

This appears to be working ok. What I'm not clear on is if the user has never logged in before (so there's nothing for Jira to remember about the last choice of selected fields), what does Jira default to (in terms of the fields displayed for that user by default)? It's possible that I missed something in the user settings or admin settings, but I have many fields enabled in both my Screen Scheme and Field Configuration, and some of these are disabled by default (for new users) in the "customize" portion of the "Create an issue" screen.

Thanks again

I am not sure : but for new users system fields should be displayed whereas custom fields are disabled by default.

Does anyone have any more information on this? We have some sophisticated screens with several custom fields. Having some of the fields hidden from them is really causing a problem, especially for our new users. Kind of a poor decision by Atlassian to hide any fields IMHO. That should be the Admin or the users decision.

I'm also still trying to find a solution of how to hide this Configure Fields option that hopefully doesn't involve putting code into each and every custom field's description.

After searching for hours on the database, I could maybe help some people


If you want to know who use that function before removing the button, this is what I done (JIRA 6)

To find the property for the toggle between ALL field and CUSTOM

select *
from app_user e,
Propertyentry pr,
Propertynumber pn
where pr.entity_id =
and =

and pr.property_key = 'jira.quick.create.use'
and pn.propertyvalue = '1'

This will get you all the user to change before removing the button


select *
from app_user e,
Propertyentry pr,
Propertytext pt
where e.user_key = 'plboucher'
and pr.entity_id =
and =
and pr.property_key = 'jira.quick.create.fields'


This is the property that contain the field checked when the CUSTOM link is click


All I did, connect on SU for all the user that I found with the first select, select ALL for all of them


Finally I removed the field, with that code in the banner


<script type="text/javascript">
(function($) {
// init on load
JIRA.bind(JIRA.Events.NEW_CONTENT_ADDED, function (e, context) {
// init on refresh




Suggest an answer

Log in or Sign up to answer
Community showcase
Published Jan 08, 2019 in Jira

How to Jira for designers

I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...

1,102 views 4 9
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you