-
Bug
-
Resolution: Duplicate
-
Low
-
4
-
Minor
-
3
-
Issue Summary
Pointing the Epic Link field to an issue where the project permissions don't allow the current user to Link Issues provides inconsistent feedback in the issue view.
Steps to Reproduce
- Given Project A has Link Issue permission restricted to only users in group Group A
- Given Project A has epic issue A-123
- Given Project B has non-epic issue B-123
- User who is not in Group A edits issue B-123 and changes Epic Link to A-123
Expected Results
Jira UI displays error, indicating that user does not have the permission to link issues in Project A. No issue change history events are recorded.
Actual Results
Jira UI updates the Epic Link field with the chosen issue key. Issue history displays that Epic Link was successfully updated. Refreshing the issue view shows that this change has not actually saved, and the Epic Link field is still empty.
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available.
- duplicates
-
JSWCLOUD-26327 Parent field is missing after being assigned by a user
- Closed
- relates to
-
JRACLOUD-82212 The Property "jira.issue.editable" still leaves the field "Epic Link" Editable
- Gathering Impact