-
Suggestion
-
Resolution: Fixed
-
30
-
122
-
Hi everyone,
Thank you for taking the time to leave feedback on this ticket. As you know, the new issue view enables Project admins to configure each custom field to either hide when empty or always be displayed. This is available in the new issue view for all Jira Cloud products (Jira Software, Jira Service Desk, Jira Core).
Learn more about configuring issue layouts
Thanks
Jira Cloud team
Hi everyone,
First off, thank you for continuing to provide feedback and sharing that you would like this feature to be implemented. Although it may take time to act on certain issues raised and we may decide to not implement something in favour of other features , we are constantly using JRACLOUD issues to look for the best opportunities to improve Jira!
With that being said, I have an exciting product update re: this feature.
As part of the new Jira issue view rollout (see blog post and documentation page to follow along.) we have updated how you can configure the layout of fields.
This includes the ability to always display a custom field, whether it has a value or not. Or, always hide that custom field This new configuration logic can be applied on a specific issue type within a specific project, across both the new next-gen projects and Classic projects (e.g. the existing Scrum and Kanban projects).
The new issue view can be enabled/disabled on a per-user basis by simply going to your avatar in the bottom right of the navigation and selecting 'Personal Settings'. From there, scroll down and see the Labs toggle to turn the new issue view on/off. Please note, this is only available for Jira Software and Jira Core projects, with Jira Service Desk coming in the future.
Ok, let's dive into how this works!
Classic Projects
The new issue view has a different overall design and information architecture, so the existing global screen configs, schemes, and field configurations were hard to map 1:1 because of a lot of existing custom logic. SO, we decided to take the fields you specified from the global screen configs and applied to an issue type within a project then let you arrange the ordering of those fields within each project!
See the Configure field layout in the issue view documentation page for how this is done. Note: You must be a Project or Site admin to 'configure' the fields on the new issue view AND the new issue view must be enabled for you.
Next-gen Projects
By default the new next-gen projects come with all the latest, awesome stuff we have built all wrapped within a project type. This includes the new configuration options and the new issue view. You cannot disable these things within next-gen projects, as they are tied together.
See the Working with next-gen software projects documentation page for more detailed information.
In these projects, the functionality is quite similar in that you have the ability to always display a custom field, whether it has a value or not. Or remove it from being seeing entirely.
Config layout logic recap - TL;DR
- You must have the new issue view enabled from your 'Personal Settings' to specify hiding/showing custom fields. If you are using a next-gen project, you don't need to worry about that as it comes with the new issue view by default.
- From the new configuration screen, you can specify how you display fields. There are 3 'buckets' to put fields into, depending on your needs for a specific project > issue type.
- Always show --> this displays the field whether or not it has a value. aka 'Primary Fields'
- Show when it has a value --> If the field has a value, it will display above the 'show more' on the issue detail view, because it has important information people should see. Otherwise, keep the field under 'show more' so people can see get to the field and add a value if they want. aka 'Secondary Fields'
- Hidden fields --> This hides the field completely from the issue detail view. For next-gen projects, you just simply remove the field.
Sorry for the long update, but wanted to give as much context and detail as I could. As I'm sure you are all aware, Jira's configuration capabilities can be quite complex. We hope you enjoy this feature, let us know how we did and/or how can we improve it!
Cheers,
Taylor Pechacek - Jira Cloud PM
As stated in JRA-1678, custom fields are automatically hidden when they are empty.
(** see my comment in JRA-1678 **)
The best solution is to provide the ability to choose whether or not to hide a field (standard or custom) when it's empty.
So it would be nice to have a flag for each field indicating if this field has to be hidden in issue views.
- blocks
-
- Closed
- duplicates
-
- Closed
-
- Closed
- is duplicated by
-
- Closed
- is related to
-
- Closed
-
- Gathering Interest
- relates to
-
- Closed
-
- Closed
[JRACLOUD-2997] Choose whether or not to hide empty custom fields from issue views
For description fields - such as those in tabs , we would like to be able to hide any fields that do not have information in them from the view screen.
Is this implemented for the Jira service desk as well?
Is there a way to completely hide the filed if there is no value to the field?
I found a workaround for those of us who are still using the classic view and want to see fields that are not populated. In short, if you set the default value to the "|" character (no quotes), then the field will show up on the main screen and it will look like it has no text in it. Then a user can click next to that field and edit it normally. Note that this does not work as cleanly in the New Issue view (it creates an empty table cell) in that field which is a little harder to fill out.
More detailed steps:
- Click Gear icon in upper right (Settings)
- Click "Issues"
- Click "Custom Fields" in left sidebar
- Navigate to the field that you want to show on the main screen, then click the three dots on the right and click "Contexts and default value"
- Click "Edit Default Value"
- Put "|" in the field with no quotes. This is the "bitwise-OR" or "pipe" character you can get by typing Shift+\
- Click "Set Default"
Now new issues you create in the old view will show that field with no text in it.
I dug a little deeper as this functionality would be highly desirable with one of our issue types. Unfortunately I was unable to find a special character that both
- Makes the fields show up in both the new and old issue views and
- show up as empty in both views.
I tried various combinations of the following special characters with no avail: <space> <newline> * _ | - # [] {} <> + . ' " ~ ` ! $ % ^ & = . I tried different combinations of the character by itself, with a space next to it, with two characters, and with a space separating the two characters, but no luck finding a good one.
TL;DR If you need the issues to look consistent between both views and show up in both views I would recommend setting the default text in the field to ' or *.
Definitely needs to be added to classic view.
New Issue view works for workflows that are very comment driven.
For workflows that are form-based it's useless.
It is those form-based views that require this capability to show empty fields.
Echoing the request to enable this for the classic issue.
Seeing the ticket moved into In Progress after the February update from Taylor, does it mean it is now being worked on for classic view? Would be great to get a timescale of when the release timeline for this looks like.
Many thanks!
Echoing the request to put this into the classic issue view. The New Issue view is not usable for us.
If you found your way here, remember to comment on Jira/Atlassian's facebook posts, too. Seems needed, since they're really trying to ignore the problem and roll-out this travesty of UX hubris.
I was involved in a product usability/feedback session with the core team. The person that interviewed me was surprised that I was having such a bad time with 'new view' that it was a hard-stop for our teams. Either Atlassian has a terrible system for listening to feedback (like these comments), or someone there is arrogantly trying to ignore it (to save their job/reputation?). It's bad, and we will all suffer unless we make it more visible.
Please address the issue ASAP for Jira Service Desk so we can display empty fields on Support tickets so me and my colleagues do not need to go and click edit on every single ticket to fill in the empty fields.
We have no plans to migrate to the New Issue View. Please implement this option for the classic issue view.
Is there a way to add some old view functionality back (i.e. choose the location of the field AND have it be hidden when empty?)
In the new view, the ticket views look really heavy if fields are empty, but if you choose to "hide if empty", the entire ticket looks super messy and unorganized. Would love to have a common middle ground!