-
Suggestion
-
Resolution: Unresolved
-
None
-
61
-
11
-
Issue Summary
Story Points custom field can be edited/viewed even though the field is removed from the Edit/View screens because under issue layout still present under Hidden fields when is Empty. This is inconsistent with most other custom fields where removing from Edit screen makes the field uneditable on Issue View.
This behaviour is by design, due to the need for Story Points field to be editable in other surfaces; but is inconsistent with behaviour of most fields - causing confusion among users and admins.
Applies to company-managed projects only; team-managed projects do not have Edit screens.
Related feature requests
There are multiple open suggestions about making specific field types uneditable. Please vote and comment on all that impact your work to help us prioritise our roadmap:
| Suggestion | Field Type | Scope |
|---|---|---|
| JRACLOUD-82368 | Team field | Make team field un-editable when removed from Edit screen |
| JRACLOUD-85094 | Story points field | Make Storypoints field un-editable when removed from Edit screen |
| JRACLOUD-82251 | Original estimate field / time tracking | Make Original Estimate field un-editable when removed from Edit screen |
| JRACLOUD-69298 | Any field | Set view/edit permissions for individual fields - field level security. |
Steps to Reproduce
- Remove Story points field from the View/Edit issue screen.
- Go to Issue Layout and move the Story points fields under Hide When Empty.
Expected Results
While the Story points field is empty does not show under More Fields in the issue View or Edit.
Actual Results
The Story points field is visible under More Fields.
Workaround
To delete the Story Points field from the issue layout but this might not meet everyone's requirements. The only other way to make Story Points un-editable is to have the whole issue/all fields be non-editable.
