Default Display of blank custom fields

[Gordon Koo]

I am currently using JIRA 6.3.4 and wish to find out if anyone has discovered a new set of source code updates that will allow blank custom fields that are contained in a JIRA request screen form to be displayed regardless of its "Null" status. 

In the past version of 6.x, there were some compares that checked whether a field was "Null" and if it was a  "Null" value the customs field would not be displayed on the screen forms. I would like all custom fields to be displayed regardless of whether the custom field contains data or is a "Null" value. I have not been able to locate the compares that make the decision as to whether a field should be displayed or not on a screen form. Any help with locating the compare source code area(s) would be appreciated.

[David Paulson · Accepted solution]

I created a support ticket to ask why fields can't be seen when they don't have a value. Basically there is an outstanding suggestion that apparently isn't high priority. Add your votes/comments to https://jira.atlassian.com/browse/JRA-2997 if you haven't already.

[Nic Brough -Adaptavist-]

It's partly historic. Because JIRA's screens are visually complex and each field makes it more so, hiding empty fields makes a lot of sense in terms of simplification. Up until the introduction of "in line edit", that point was pretty much inarguable - why bother users if they don't need it. But inline edit (partly) invalidates it because you want to get to the empty fields now. Atlassian haven't budged on this yet, but I'd like to see *at least* some obvious indication of empty fields. My thought was a contracted box full of them with a title like "Empty fields" - expand the area, see all of them, and then click to in-line edit. There's probably a much better approach, that's just my idea.

[Marci Boecking]

It's disappointing to find out that Atlassian has STILL not addressed this issue.  Users need to be able to edit fields on the viewing of a page.  Making fields invisible just because they are null doesn't mean they should never be seen or will always need to have null values.  It's very difficult to enter values into those fields once the tickets are created.  Usability 101!!

[Linda Wanitschek]

boy do we sure want this implemented.  so frustrating 

[Corey Jepson]

Still want this in 2019

[Eric S.]

Another me too thread... well... me too :)

[David Paulson]

I would like to know as well

[Darrel Jackson]

I'm on v6.5

[Darrel Jackson]

I'm keen to know too.