-
Suggestion
-
Resolution: Unresolved
-
80
-
66
-
Summary:
Since the new issue view supports Inline editing there is no need to have a separate Edit Issue Screen unlike in the Old Issue View where the edit issue screen was accessed via the EDIT button. Currently, Edit Issue Screen and View Issue Screen are dynamically loaded as we have the inline editing feature.
However, Incase a JIRA Admin chooses to have a Separate View and Edit Issue Screen, then there could be unusual things that can be seen on the JIRA issue.
Steps to Reproduce:
- In a Project Create a Screen Configuration where View Issue Screen and Edit Issue Screen is different
- Consider Two tabs (TA, TB) and 2 fields inside Each tab (F1, F2, F3, F4). Tabs are not necessary always to show this behavior but it's better for this example.
- In the View Issue Screen add TA and under this tab add F1 and F2. Then Add TB and under this tab add F3 and F4
- In the Edit Issue Screen add TA and under this tab add F1 and F2. Do not add the TB tab or the F3, F4 fields in the Edit Issue Screen.
- Go to the Issue View and you will only see the TA tab and F1 and F2 fields under it. The TB tab and F3, F4 fields are not shown even though they are in View Issue Screen.
This is due to the fact that the TAB and the field were not added to the "Edit Issue Screen".
NOTE: In the Issue Layout Fields are not added to the "Hide fields When Empty" section.
Customer Scenario:
- In a Scenario where (Without using a Read-Only field) we would want to see the F3, F4 fields in the TB tab, but don't want any user to edit it. It would be helpful to display the fields as Empty/Null when they are just added to the View Screen and Not Edit Screen.
- Then through a Workflow Transition screen, those fields could be updated by only a few users who meet the condition of a Workflow Transition.
Suggestion:
- When a Field is added to the View Screen and not the Edit Screen, With proper project permissions the field needs to be visible/viewable even if the field value is Null.
Workaround
1) For some custom field types such as Short Text, adding a default value to the field will make it appear even if you don't have the field on the Edit screen. You still must add the field to the Edit screen if you want to edit the field, however.
2) Pin the custom field to have it display while empty - only works for users who pinned the custom field.
- duplicates
-
JRACLOUD-79015 Unable to view empty custom field when its not included in the Edit Issue Screen
-
- Closed
-
- is related to
-
- Gathering Interest
-
- Gathering Interest
- relates to
-
- Closed
- supersedes
-
JRACLOUD-75411 FixVersion field is shown then hidden when a user without Resolve issue permission views an issue
-
- Closed
-
[JRACLOUD-78320] Issue Fields that are empty Do Not show up in the Issue View if they are added to View Screen but not in Edit Screen Config
Note;
Tested on a Number field type, and the workaround provided does not work.
Hi team,
There are no many comments on this issue, but this is definitely a bad experience for end users.
In our case, we use a field to add an ID from an external process for some integrations.
The team that runs the audits don't have an easy way to know if the field is not in the project screens, or if is empty or not, in a friendly way, so every time they need to spend part of their day following different paths to understand what is going on.
On a high level, the UX of this feature is not at all good.
I agree with YARON LEVY on this. This seems more like a bug to me than a suggestion.
In my issue layout I have a field shown under the 'Context Fields' section. Not in the 'Hide when Empty' section, not dragged off to the left to hide / remove it. It's sitting in the middle of my list of context fields and it's not showing because it is not editable (gets updated automatically via other field values)
So why is it hidden? If I drag that field into the 'Description' fields section, it shows up even though it's not editable. Why does it disappear when in the context fields? BUG!
It is essential.
The current state is a misbehaviour as I see it. Especially, when you have the Issue layout config, with the explicit way of whether to hide or show empty fields. So, if I choose the empty field should be shown, and it is on the view screen, it should be on screen.
If it is on the View, it should be visible. Just put it's name label on the HTML, on the place and Tab it belongs.
Many thanks.
Kindly change this issue type from Suggestion to Bug.