Details
-
Bug
-
Resolution: Fixed
-
Low
-
3.13.3
-
3.13
-
Description
When an issue is moved from one project to another, its subtasks also get moved to the new project.
If the new project uses an issue type scheme and workflow scheme that is different from the original project then subtasks need to be migrated.
1. In the MoveIssueUpdateWorkflow screen the wrong target workflow is displayed. Currently the parent issue's target workflow is being displayed, rather than the subtask's target workflow. (i.e. displays "Workflow Apple -> jira" rather than "Workflow Apple -> Workflow Bacon")
2. The list of target statuses is based on the parent issue's target workflow.
3. The subtask gets migrated to the parent issue's workflow. (i.e. after the move is complete the workflow actions are those of the parent issue's issue type rather than the subtask's issue type)
Attachments
Issue Links
- is duplicated by
-
JRASERVER-18565 Moving issue with sub-task leads in target project to workflow/issue type violation
- Closed