-
Type:
Bug
-
Resolution: Won't Do
-
Priority:
High
-
Component/s: Space - List
-
6
-
Severity 3 - Minor
-
81
Issue Summary
Fields that are not present on the Edit Screen can still be edited by users from the List View (issue navigator) in Jira Cloud, provided they have "Edit Issue" permissions. This contradicts the screen scheme’s behavior and poses a governance challenge.
Steps to Reproduce
- Create a custom field and associate it only with the View and Create screens, excluding it from the Edit screen.
- Navigate to the List View (issue navigator) and expose this custom field via the column configuration.
Expected Results
The field should appear as read-only or non-editable in the List View if it’s not part of the Edit screen.
Actual Results
Users are still able to inline edit the field directly from the List View, even though it's excluded from the Edit screen configuration.
Workaround
Use "All work" tab to manage work items. We're working on merging the List and All work into one view - https://community.atlassian.com/forums/Jira-articles/We-re-merging-List-and-All-work-one-powerful-view-for-all-teams/ba-p/3090105
- relates to
-
JRACLOUD-97873 Convert to Work Item - bypassing the UI-level restriction set in the Screen Scheme
-
- Gathering Impact
-
-
JRACLOUD-97891 Bulk Move flow - bypassing the UI-level restriction set in the Screen Scheme
-
- Long Term Backlog
-
- is action for
-
SAM-3174 Loading...