Severity 3 - Minor
In Jira Software Server you can restrict editing authorization per status (e.g. Approved) to a particular group by setting "jira.permission.edit.group" to a particular group (e.g. Approvers). It means, that only users belonging to the group "Approvers" can edit an issue when it is in status "Approved". Creating an Epic Link requires edit permissions for both linked issues. When you try to create an Epic Link as a user, that is not a member of the group specified in "jira.permission.edit.group" setting your attempt will fail (which is expected). Unfortunately, message confirming successful creation of an Epic Link will be displayed anyway. It is misleading and confusing.
Steps to Reproduce
- Create a group "Approvers" (user, that you use to reproduce this steps must not be in this group).
- Set property of a status (e.g. "Approved") in project's workflow: jira.permission.edit.group.1 -> Approvers.
- Create an Epic (e.g. ABC-100).
- Create a Story (e.g. ABC-200) and keep it in Backlog.
- Move the Epic to Approved status.
- Edit Story -> Put "ABC-100" in Epic Link field.
- Click on "Update" button (bottom-right).
- Pop-up will be displayed "ABC-200 has been updated".
- Verify that no link has been created in Epic nor Story.
Message stating, that Epic Link creation failed due to lack of required permissions.
The below confirmation message is displayed:
ABC-200 has been updated
- Do not use "jira.permission.edit.group" setting.
- Add user to the group specified in "jira.permission.edit.group" setting.
- Add a group, that the user is a member of to "jira.permission.edit.group" setting.
- has a regression in
JSWSERVER-20770 Unable to link Epic without Edit Issue permissions
- relates to
JRASERVER-71995 CSV Import for Subtasks with Epics is failing for user in 8.13.1 whereas the same CSV file successfully imports in 8.5.1
- is cloned by