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

          Form Name

            [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

            597beb9eaea9 can you please create a Support Ticket with us so we can investigate? Please reference this bug (https://jira.atlassian.com/browse/JSWCLOUD-16752) in your ticket. Thank you!

            Anusha Rutnam added a comment - 597beb9eaea9 can you please create a  Support Ticket  with us so we can investigate? Please reference this bug ( https://jira.atlassian.com/browse/JSWCLOUD-16752 ) in your ticket. Thank you!

            We are also experiencing this issue still. We are currently on Jira cloud. 

            Jeanna Knowles added a comment - We are also experiencing this issue still. We are currently on Jira cloud. 

            30f1479b99b8 and fe99f810edec can you please create a Support Ticket with us so we can investigate? Please reference this bug (https://jira.atlassian.com/browse/JSWCLOUD-16752) in your ticket. Thank you!

            Anusha Rutnam added a comment - 30f1479b99b8 and fe99f810edec  can you please create a Support Ticket with us so we can investigate? Please reference this bug ( https://jira.atlassian.com/browse/JSWCLOUD-16752 ) in your ticket. Thank you!

            The Bug is closed but I am still facing this particular issue. Can anyone help me resolve this?

            Digesh Bhatt added a comment - The Bug is closed but I am still facing this particular issue. Can anyone help me resolve this?

            Ted added a comment -

            Same issue here, with enhanced backlog and board enabled. The tasks are identical to others (Epic>Task>Subtask) but for some reason show in the "issue without epics" lane at the bottom. 

            Ted added a comment - Same issue here, with enhanced backlog and board enabled. The tasks are identical to others (Epic>Task>Subtask) but for some reason show in the "issue without epics" lane at the bottom. 

            Hi everyone who has commented recently - can you please create Support Tickets with us so we can investigate further? If you are admins on multiple sites, make sure to create the ticket in association with the site on which you continue to see this behaviour. Thank you.

            Anusha Rutnam added a comment - Hi everyone who has commented recently - can you please create Support Tickets with us so we can investigate further? If you are admins on multiple sites, make sure to create the ticket in association with the site on which you continue to see this behaviour. Thank you.

            Hi ! We enabled the new experience (it's nice), and still we are facing this issue.

            Benoit Delbos added a comment - Hi ! We enabled the new experience (it's nice), and still we are facing this issue.

            Even with activated "Enhance my board and backlog", it still exists.

            Sub-tasks are showing as "Issues without Epic" even if the parent task contains Epic.

            Is there any solution? Workaround?

            P.S. It works fine if the parent of the sub-task is assigned to the same user and a sub-task. But it would not fit our workflow.

            Anton Kryzhanovskyi added a comment - Even with activated "Enhance my board and backlog", it still exists. Sub-tasks are showing as "Issues without Epic" even if the parent task contains Epic. Is there any solution? Workaround? P.S. It works fine if the parent of the sub-task is assigned to the same user and a sub-task. But it would not fit our workflow.

            Jacques Dussault added a comment - - edited

            We still have this issue. It may solve it in the new board (TBD) but is not fixing the core issue since Structure still shows some stories as "No Epic" even if they have one.

            Jacques Dussault added a comment - - edited We still have this issue. It may solve it in the new board (TBD) but is not fixing the core issue since Structure still shows some stories as "No Epic" even if they have one.

            Hi

            If I take the steps as described it works fine on the new enhanced board, if you still use the old board style the sub-task will still show as an issue without an Epic

            You need to switch to the new Enhanced board

            Marc - Devoteam added a comment - Hi If I take the steps as described it works fine on the new enhanced board, if you still use the old board style the sub-task will still show as an issue without an Epic You need to switch to the new Enhanced board

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

                Created:
                Updated:
                Resolved: