Users lacking the 'Edit Issues' permission are not able to link an Epic to newly created or existing issues. However, despite an error message when performing this action, a new issue is still created and the workflow is left in a broken state for that issue.
This issue was introduced in JSW 8.11.0 and is not occurring in 8.10.1.
- Create two Software projects.
- Remove 'Edit Issues' permission in the Project A permission scheme.
- Create an Epic in 'Project A'.
- Create a new issue (or edit existing issue) in 'Project B' with the Epic Link assigned to the Epic created in step 3.
The issue is not created because the user does not have the appropriate permission. See
JSWSERVER-13986 for a related suggestion.
Jira Software considers linking issues to epics as editing the scope of work of an epic, which is why it uses the "Edit issue" permission to check if a user is able to link/unlink issues to an epic.
As of 8.11, the user gets an unclear error message that is shown in the screenshot and the impression the issue isn't submitted:
- The issue is created without the Epic Link or required fields.
- The os_wfentry.state for the issue is set to 0 so no workflow transition button appears on the view issue screen.
|10601||Software Simplified Workflow for Project SCRUM||NULL||0|
The workaround is to:
- Search for the new issue – either by direct URL or through the database.
- Add the required fields and Epic Link (under a user that has permission).
- Fix the workflow with the KB Workflow transition button missing from the issue view page in Jira server.