Users with "Browse Only" access rights need to be able to see all the information on a ticket. Even if that information is empty.  That's we already have the "Hidden" section. 

Also, as a Jira admin who does not have "edit" permissions on projects, it's impossible to validate if your newly added field has been added correctly. Also, the "Where is my field" checker, also does not show any errors. All checks are green, but still my field is not visible.

This needs to be fixed.

Why offer Administrators the ability to configure "Hide when empty" if Atlassian will override that choice? It's probably more nuanced than that (tab configuration vs description field configuration). There's probably performance reasons that you do this, too, but this causes confusion for Users.

Please consider implementing "Hide when empty" logic for the entire issue view.

I also need that read-only useers can see empty fields ! 

I raised a support request about this as I needed to see the value for a field and wasn't sure if it was empty or just not configured on my screen.

I did find that if you viewed an issue where the field had a value, then pinned the field, that on viewing an issue where the field was empty that it now shows the field with the text "none" against it. So that would be a possible workaround, but also makes the current behaviour inconsistent and strongly implies that this is a bug report, not a feature request.

For a user with only "browse projects" permission, in addition to not seeing empty fields, the new view shows the option to "Create Subtask" on an Epic, which should not be there.  If you try to use that option, you get a server error pop up.

Hi everyone,

I am moving this to a suggestion as this is intended behaviour. Will keep this ticket open to gather impact and feedback. 

Hiding empty fields is incorrect, just because a field does not have a value does not mean it should be omitted from view entirely, it is important to show which field have been considered and not filled in. Simply hiding empty fields leaves the viewers unaware as to what are the reasons behind why they cannot see the field, like:

1. They don't have permission
2. Not applicable to project
3. Has empty value

Moreover the user experience for users with view permission starts to differ from those with edit permission, as those with view permission will only see fields which are populated, while those with edit permission get to see field which were left blank. And its important to know whether a field is left blank or if its hidden for permission/applicability reasons.