-
Bug
-
Resolution: Fixed
-
High
-
28
-
Severity 3 - Minor
-
21
-
Summary
When implementing the property(jira.issue.editable) in a status, it seems that we are still able to edit the issue in new issue view.
Moving it back to old issue view does show that the issue is not editable.
Implementing "jira.permission.edit.denied " also does not seem to work in new issue view.
Steps to Reproduce
- Go to a workflow
- Click on a status, and click on properties
- Add "jira.issue.editable" as key and "false" as value
- Go to an issue and transition to the status that has the property
Expected Results
The issue then becomes not editable
Actual Results
The issue is still editable
Note
Same result on Jira mobile application
Workaround
Currently, there is no workaround available
- is duplicated by
-
JRACLOUD-73758 New issue view Assignee editable when Editable property set to false
- Closed
- is related to
-
JRACLOUD-75321 Workflow property edit.deny.projectrole removes the permission from all users
- Closed
-
JRACLOUD-12244 Allow control of whether comment field will be shown on Edit and Transition screens
- Gathering Interest
- causes
-
JIV-14117 Loading...
- depends on
-
BENTO-4401 Loading...
- has action
-
JIV-14575 Loading...
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...