-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Medium
-
Component/s: Issue - Backend
-
11
-
Severity 3 - Minor
-
0
Issue Summary
Converting a subtask to issue with sprint filled while having no Schedule Issues or Manage sprints ends in a generic 500 error.
Steps to Reproduce
- Have a subtask with the sprint field filled (non-empty)
- As a user who has no permissions to Schedule Issues or Manage sprints, try converting the subtask to issue.
Expected Results
Jira should tell you are not allowed to change the issue given that you do not have Schedule Issues or Manage sprints permission.
Actual Results
An unidentified 500 error is displayed.
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available
- is related to
-
JRACLOUD-78694 Converting a standard issue to subtask will end in a generic 500 error if the new parent Sprint field is populated
-
- Closed
-