Hello,
I needed a field with labelling-behaviour with a custom name. Since I wouldn't change the name of the system standard field "Labels", I am using a custom field of type: label now.
The problem is, that is won't show up on the standard issue view, if it has no value.
In a nutshell: I want my custom field to behave the usual way like the field "Labels" does: showing up although and displaying "none". So it would be clickable and editable on the fly.
Any ideas, someone?
as of now we can't show the custom field if it is empty, check the following issues
https://jira.atlassian.com/browse/JRA-6697
https://jira.atlassian.com/browse/JRA-2997
if you want to display the custom fields then set some default value
That doesn't work for me. I want to show "Sprint", which is locked by Jira Agile.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This functionality is not desirable. I want to provide the user the knowledge of the custom field without knowing exactly how to set it.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yep, typical Atlassian answer:
Created: 20/Jan/2004 11:29 AM
"We have revisited this issue again recently and wanted to highlight that there are still currently no plans to implement this suggestion, and it is not currently on any JIRA team’s roadmap at this stage."
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Why?
I'd ned to add a textbox and label-box to my issues and let other users to fill-in appropriate values. Yet not having them visible on view screen is quite inconvenient.
Currently we use "naming conventions" and put these information to Issue Name ... also inconvenient, but practical. Custom fields would have make it much better ...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
New Answer
You can do this now in the new JIRA issue view. Steps:
Now it will always show in the new view. For people still using the old view, see my original answer below.
Original Answer
This seems to work: https://community.atlassian.com/t5/Jira-Core-questions/How-can-I-display-empty-custom-fields/qaq-p/445311#M33862
Basically, make the default two spaces, and then the field will always show up.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I was hopeful that this would be a workaround, but it doesn't seem to work in Jira Software (server) 7.12.1.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I got it working! My company has permitted me to open-source my solution:
https://github.com/theschles/JIRA_ScriptRunner_AlwaysDisplaySelectList
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Philip, I retrieved your piece of Code. Thanks. I try to tweak it as I my scripted field should return User Picker (multiple users) and not HTML as yours. Any idea where I should start (I'm not a real programmer, just helping the team with jira because oh the holidays ;) ) thanks Julien
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This only works for select lists, right? I was hoping for something for text areas.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Another workaround to a silly problem.
If you are using a USERPICKER.
Create a place holder user named "Select User" (obv pick whatever name you prefer)
Set that user as the default value (https://jira.hotschedules.com/secure/admin/ConfigureCustomField!default.jspa?customFieldId=XXXXXXX)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello
I changed my Default value from "none" to " SELECT TOPIC" this way when ever a new ticket was raised the custom field would display and the users can pick a TOPIC from the drop down. using BLCK CAPS for this entry and upper- lower case for the options helped them notice the option.
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.