-
Bug
-
Resolution: Fixed
-
High
-
None
-
7
-
Severity 3 - Minor
-
Issue Summary
When you try to move issues with subtasks from a Team-managed project to a company-managed project it returns an error 500.
Steps to Reproduce
- Select issues from a team-managed project, ideally all issues.
- Try to perform a bulk move.
- Error 500 is returned before the "map subtask" screen.
Expected Results
Not return error 500 and move the issues from one project to another.
Actual Results
Error 500 screen and action not performed.
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available
- is related to
-
JRACLOUD-71354 Moving a Jira task with sub-tasks to another project throws an error
- Closed
-
JRACLOUD-72140 Bulk operation in Next-Gen issues returns error 500
- Closed
-
JRACLOUD-71470 Some bulk operations that involve sub-tasks can fail with error 500
- Closed
-
JSWCLOUD-17979 Using "Move" option on sub-task of a next-gen projects returns 500 error
- Closed
-
JRACLOUD-72214 Using bulk operations to move parent tasks (with sub-tasks) from next gen to classic project returns error
- Closed
- mentioned in
-
Page Loading...