-
Bug
-
Resolution: Won't Fix
-
Highest
-
None
-
7.13.18, 8.5.15, 8.13.7, 8.18.0, 8.20.4, 8.20.6, 8.20.9, 9.4.0, 9.4.1
-
None
-
7.13
-
16
-
Severity 2 - Major
-
216
-
-
Issue Summary
When the ability to create issues has been disabled via workflow permission for all users, one can still create a new issue via the GUI. The REST API disallows this (which feels like the correct behavior).
Steps to Reproduce
- Edit the workflow of issue type T in project P
- Click View Properties at the initial step e.g. Open
- Add this property:
Key: jira.permission.createissue.denied Value: true
- Publish the workflow
- Attempt to create a new issue P-1 via the GUI using issue type T in project P
- Attempt to create another issue via the REST API.
Expected Results
No new issues can be created, as this ability has been disabled by the workflow permission.
Actual Results
A new issue can still be created via the GUI (using the "Create" button or the inline issue create functionality).
However, Issues cannot be created via the REST API or via the "clone" button in the GUI. The workflow permissions are only being ignored when creating new issues in the GUI.
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available
- causes
-
JRASERVER-67652 Using jira.permission.createclone.denied on Initial Workflow Status breaks Issue Creation via REST API
- Closed