Details
-
Bug
-
Resolution: Unresolved
-
Low
-
None
-
1
-
Severity 3 - Minor
-
Description
Issue Summary
Incorrect Entry on the Issue History Tab for Epic Link field.
Steps to Reproduce
- Allow user to have Edit issue permissions for Issue A (Project A) but not for Issue B (Project B)
- Allow Browse projects permission for both the projects.
- Try to edit Parent field of Issue A with Issue B. Since the user has browse projects permissions in both the projects, user can see Issue B in the Parent field dropdown and make the change.
- But this is invalid action since the user does not have edit issue permission for issue B. So upon browser refresh, Parent field will be empty.
- But if you check the History tab, following entry will appear:
User updated the Epic Link
None -> Issue B
Expected Results
There should be no entry in the history tab.
Actual Results
Entry in the history tab for Epic Link
User updated the Epic Link
None -> Issue B
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available
Attachments
Issue Links
- is caused by
-
JRACLOUD-83531 Adding an issue to an epic silently fails if the user doesn't have Edit Issues permission for both the epic and the child issue
- Closed