Uploaded image for project: 'Jira Platform Cloud'
  1. Jira Platform Cloud
  2. JRACLOUD-90722

Sub-tasks of a TMP issue are not displayed under its parent Sprint on a CMP board.

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Not a bug
    • Icon: High High
    • Backlog - Sprints
    • None

      Issue Summary

      The company-managed board that fetches issues from Team-managed projects displays different behavior for issues when moving them from Backlog to a Sprint based on the project type of the issues.

      Team-managed issues: When moving issues from Backlog to a Sprint on Scrum backlog, only the parent issue is displayed under the Sprint and the sub-tasks move back to the backlog.

      Steps to Reproduce

      1. Create a Filter that fetches issues and their sub-tasks from any TMP.
      2. Create a new Scrum board using the Filter created in Step 1.
      3. Create a Sprint in the new board created.
      4. Move the parent issue and its sub-task from the Backlog to the Sprint created.
      5. Reload the page to see that the sub-tasks are moved back to the Backlog.

      Expected Results

      When a Parent issue is moved to a Sprint, its sub-tasks need to be automatically moved to the same Sprint.

      Actual Results

      Parent issue is displayed under the required Sprint, but its sub-task is displayed under the Backlog which is not the expected behavior.

      Workaround

      Currently, there is no direct workaround for this behavior. A workaround will be added here when available.

      However, if the display problem is causing major confusion in the environment, you can either ensure to only manage TMP issues on their respective board or Migrate the team-managed to company-managed project.

              Unassigned Unassigned
              b4b218cdd0b3 Vaishnavi
              Votes:
              4 Vote for this issue
              Watchers:
              11 Start watching this issue

                Created:
                Updated:
                Resolved: