Details
-
Bug
-
Resolution: Unresolved
-
Medium
-
None
-
1
-
Severity 3 - Minor
-
Description
Problem
When moving Standard type issues of the Team Managed Jira Work Management project (along with subtasks) from the Backlog section to the Sprint section on a Scrum board, the parent issue moves along with the subtask initially. However, after refreshing the Scrum board, the subtask is shown under the Backlog sections and not under the sprint.
Environment
Team Managed Jira Software project
Team Managed Jira Work Management project
Steps to Reproduce
- Create a TMP JWM/JS project.
- Create a Standard issue.
- Create a subtask under the standard issue.
- Create a Scrum board for this project and place it in your profile.
- Go to the Backlog.
- Create a sprint.
- Move the standard issue from the scrum backlog to the newly created sprint.
- The Standard issue moves along with the subtask and the Sprint field is updated in both the issues.
- Refresh the board-
The sprint value stays in both the issues but the subtask is now shown under backlog.
- The subtask is shown under Backlog and not under Sprint.
Expected Results
Subtask should stay in Sprint
Actual Results
Subtask moves out of Sprint and when try to remap to Sprint we get the below error
Workaround
Notes
Attachments
Issue Links
- relates to
-
JSWCLOUD-26207 Ability to have Team Managed Project (TMP) Subtasks shown in the Company Managed Project (CMP) Active sprint board when directly creating from Parent issue.
- Gathering Interest
- mentioned in
-
Page Loading...