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

Sub-tasks created inside a custom standard issue type appear as 'issues without epic' when using swimlanes based on epics on a board

      Atlassian status as of Aug 2023

      Hello all,

      We've brought an enhanced board and backlog to Company-managed Projects which has resolved this bug https://community.atlassian.com/t5/Jira-Software-articles/Enhanced-Jira-board-and-backlog/ba-p/2331946

      Thank you,
      Eoin Ryan
      Product Manager

      Summary
      Sub-tasks created inside a custom standard issue type appear as 'issues without epic' when using swimlanes based on epics on a board

      Environment

      Steps to Reproduce

      1. create an epic and assign it to user1
      2. create a custom standard issue type inside the epic and assign it to user1
      3. create a sub-task inside the custom standard issue type and assign it to user2
      4. go to the project board and change its settings to show the issues using swimlanes based on epic
      5. go to the board and use the filter 'Assignee' and select the assignee of the sub-task (user2)

      Expected Results
      The sub-task will appear under the respective epic

      Actual Results
      The sub-task will appear at the end of the board as 'issues without epic'

      Workaround
      No workaround at the moment

            [JRACLOUD-86257] Sub-tasks created inside a custom standard issue type appear as 'issues without epic' when using swimlanes based on epics on a board

            Kate Durnell made changes -
            Component/s Original: Classic - Board Configuration [ 46719 ]
            Component/s Original: Board (Company) - Kanban Board [ 61958 ]
            Component/s New: Board (Company) - Configure Board - General [ 77992 ]
            Component/s New: Board (Company) - View [ 77904 ]
            Key Original: JSWCLOUD-16752 New: JRACLOUD-86257
            Project Original: Jira Cloud [ 18511 ] New: Jira Platform Cloud [ 18514 ]
            sguio made changes -
            Labels Original: jsw-monitor uif New: jsw-monitor legacy uif
            Austin Shen made changes -
            Resolution New: Cannot Reproduce [ 5 ]
            Status Original: Gathering Impact [ 12072 ] New: Closed [ 6 ]
            SET Analytics Bot made changes -
            UIS Original: 103 New: 106
            SET Analytics Bot made changes -
            UIS Original: 102 New: 103
            SET Analytics Bot made changes -
            UIS Original: 204 New: 102
            Hannah Charak (Inactive) made changes -
            Status Original: Needs Triage [ 10030 ] New: Gathering Impact [ 12072 ]
            Anusha Rutnam made changes -
            Resolution Original: Fixed [ 1 ]
            Status Original: Closed [ 6 ] New: Needs Triage [ 10030 ]
            Christopher Kennedy made changes -
            Comment [ This issue still persists with the enhanced board. It is not resolved. ]
            Eoin made changes -
            Description Original: {panel:title=Atlassian status as of May 2023|borderStyle=solid|borderColor=#b2d4ff|titleBGColor=#b2d4ff|bgColor=#eaf1fc}
            Hello all,

            We'll be bringing an enhanced board and backlog to Company-managed Projects in the next few months which will resolve this bug https://community.atlassian.com/t5/Jira-Software-articles/Enhanced-Jira-board-and-backlog/ba-p/2331946

            Follow the updates on our public roadmap https://www.atlassian.com/wac/roadmap/cloud/board-and-backlog?status=comingSoon&category=agileDevOps&selectedProduct=jsw&p=66921ae1-63

            Thank you,
            Eoin Ryan
            Product Manager
            {panel}



            *Summary*
            Sub-tasks created inside a custom standard issue type appear as 'issues without epic' when using swimlanes based on epics on a board

            *Environment*

            *Steps to Reproduce*
            # create an epic and assign it to user1
            # create a custom standard issue type inside the epic and assign it to user1
            # create a sub-task inside the custom standard issue type and assign it to user2
            # go to the project board and change its settings to show the issues using swimlanes based on epic
            # go to the board and use the filter 'Assignee' and select the assignee of the sub-task (user2)

            *Expected Results*
            The sub-task will appear under the respective epic

            *Actual Results*
            The sub-task will appear at the end of the board as 'issues without epic'

            *Workaround*
            No workaround at the moment
            New: {panel:title=Atlassian status as of Aug 2023|borderStyle=solid|borderColor=#b2d4ff|titleBGColor=#b2d4ff|bgColor=#eaf1fc}
            Hello all,

            We've brought an enhanced board and backlog to Company-managed Projects which has resolved this bug https://community.atlassian.com/t5/Jira-Software-articles/Enhanced-Jira-board-and-backlog/ba-p/2331946

            Thank you,
            Eoin Ryan
            Product Manager
            {panel}



            *Summary*
            Sub-tasks created inside a custom standard issue type appear as 'issues without epic' when using swimlanes based on epics on a board

            *Environment*

            *Steps to Reproduce*
            # create an epic and assign it to user1
            # create a custom standard issue type inside the epic and assign it to user1
            # create a sub-task inside the custom standard issue type and assign it to user2
            # go to the project board and change its settings to show the issues using swimlanes based on epic
            # go to the board and use the filter 'Assignee' and select the assignee of the sub-task (user2)

            *Expected Results*
            The sub-task will appear under the respective epic

            *Actual Results*
            The sub-task will appear at the end of the board as 'issues without epic'

            *Workaround*
            No workaround at the moment

              eryan Eoin
              msoliz@atlassian.com Mauricio S (Atlassian)
              Affected customers:
              239 This affects my team
              Watchers:
              167 Start watching this issue

                Created:
                Updated:
                Resolved: