-
Suggestion
-
Resolution: Unresolved
-
50
-
13
-
Hi everyone,
Thanks for taking the time to leave feedback on this ticket.
We’ve reviewed your comments, investigated the original intent for this behavior, and concluded that the ability to edit story points in the work item view — even when removed from the Edit issue screen — is an intentional choice. As long as one field is editable on a screen, story points will be editable.
Many teams rely on the story points field to be editable across all scenarios (including subtasks without screens), and keeping this behavior avoids significant and large-scale configuration changes for many customers.
If you need to restrict or hide story points, you can:
- Hide in the work item view — Remove story points from the layout.
- Hide in child issue tables — Use Configure columns to uncheck story points.
- Limit to specific issue types — Create a custom field context for only the desired types or projects.
We appreciate that this may not be a perfect fit for every workflow, and we are tracking feedback to understand if a broader change is warranted in the future.
If you’d like, I can also add your feedback to the internal request so our product team is aware of your exact use case.
Kindest,
Ahmud
Product Manager for Jira Cloud
Issue Summary
The Story Point field is editable in the new issue view although the field does not exist in the edit issue view.
Steps to Reproduce
- Create a new screen for Edit issue view
- Remove Story point field from the screen
- Edit the issue the Story point field is editable in the new issue view
Expected Results
The Story point should not be editable in the New Issue View
Actual Results
The Story point is editable in the New Issue View
Workaround
No workaround available
- is related to
-
JRACLOUD-76349 Story Points custom field can be edited/viewed even though the field is removed from the Edit/View screens
- Closed