Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-10683

Display sub-task under an epic swimlane if a parent issue is hidden.

XMLWordPrintable

    • 6.03
    • 13
    • Severity 3 - Minor
    • 55
    • Hide
      Atlassian Update – 11 Oct 2019

      Hi everyone,

      We apologise for taking that long to revisit this issue. The estimate for resolution provided in the previous status update has been long exceeded. As Atlassian values openness, let us bring clarity to this case and explain how we currently deem the bug.

      The last time we investigated it, we have decided that neither its impact nor the interest it had gathered were sufficient for us to prioritise fixing it. We have now examined it once again and reached the same conclusion. The fact that the impact and interest growth trends have remained steady since the previous evaluation only confirms that we made the right call. This and our current product priorities are the reason why we are once again deciding not to include it in our bug fix plans for the foreseeable future.

      The bug will remain in the "Long term backlog" status. It denotes that while currently it is not as severe nor pervasive as other issues, it is within the cohort of bugs which are the strongest candidates for being included in the bug fix roadmap during future reevaluations of it.

      We understand how disappointing this decision may be, but we hope you will appreciate our transparent approach and communication. To understand how we organise and prioritise bug fix work I encourage you to read Atlassian Server Bug Fix Policy. More importantly, if you would like to find out what the Jira team is currently focused on and has recently delivered see the following dashboards:

      Atlassian will continue to watch this issue for further updates, so please feel free to share your thoughts in the comments.

      Thank you,
      Pawel Drygas,
      Jira Server Bug Fix Team

      Show
      Atlassian Update – 11 Oct 2019 Hi everyone, We apologise for taking that long to revisit this issue. The estimate for resolution provided in the previous status update has been long exceeded. As Atlassian values openness, let us bring clarity to this case and explain how we currently deem the bug. The last time we investigated it, we have decided that neither its impact nor the interest it had gathered were sufficient for us to prioritise fixing it. We have now examined it once again and reached the same conclusion. The fact that the impact and interest growth trends have remained steady since the previous evaluation only confirms that we made the right call. This and our current product priorities are the reason why we are once again deciding not to include it in our bug fix plans for the foreseeable future. The bug will remain in the "Long term backlog" status. It denotes that while currently it is not as severe nor pervasive as other issues, it is within the cohort of bugs which are the strongest candidates for being included in the bug fix roadmap during future reevaluations of it. We understand how disappointing this decision may be, but we hope you will appreciate our transparent approach and communication. To understand how we organise and prioritise bug fix work I encourage you to read Atlassian Server Bug Fix Policy . More importantly, if you would like to find out what the Jira team is currently focused on and has recently delivered see the following dashboards: Jira Server and Data Center: Recently resolved issues Jira Server and Data Center: Current work and future plans Jira Server and Data Center: Bug Fix Board Atlassian will continue to watch this issue for further updates, so please feel free to share your thoughts in the comments. Thank you, Pawel Drygas, Jira Server Bug Fix Team

      Summary

      Sub-tasks should be shown on the epic swimlanes if the parent issue is hidden by a quick filter.

      Steps to Reproduce:

      1. Assign parent issues to an epic.
      2. Create sub-task on a parent issues.
      3. Add parent issue to an active sprint
      4. Configure scrum board for epic swimlanes
      5. Add a quick filter that hides the parent issues but does not hide the sub-task.
      6. Go to work mode and apply the quick filter from step 5.

      Actual Behavior:

      Sub-task is displayed on a swimlane "Issues without an epic".

      Expected result:

      Sub-task must be shown on the epic swimlane from the parent issue. The Epic swimlane remains visible after applying the quick filter.

            [JSWSERVER-10683] Display sub-task under an epic swimlane if a parent issue is hidden.

            Daisy Eady added a comment -

            +1

            Daisy Eady added a comment - +1

            Peter Gustavsson added a comment -

            +1

            Peter Gustavsson added a comment - +1

            Justin Griffith added a comment -

            +1

            Justin Griffith added a comment - +1

            Kristi Johnson added a comment -

            +1

            Kristi Johnson added a comment - +1

            Josep Salom added a comment -

            +1

            Josep Salom added a comment - +1

            vlad added a comment -

            if only Atlassian would look at these comments and provide response ! Seems like a wishful thinking 

            vlad added a comment - if only Atlassian would look at these comments and provide response ! Seems like a wishful thinking 

            Evgeniy Nikanorov added a comment -

            Very usefull request!

            I have board based on Epic swimlines. There we see issues and subtasks.

            Work is organized on priorities by Epic (top priority Epic is first on roadmap and first on the board).

            If issue go out from current board (to another department for example) unclosed subtasks drops-down from first priority swimline to "Issues without Epic" at the bottom of the page. It's very-very unplesant behabiour.

            Possible solutions:

            • add "Epic link" to subtasks
            • keep them under Epic swimline at least (regardless of the parent issue visibility)

            Evgeniy Nikanorov added a comment - Very usefull request! I have board based on Epic swimlines. There we see issues and subtasks. Work is organized on priorities by Epic (top priority Epic is first on roadmap and first on the board). If issue go out from current board (to another department for example) unclosed subtasks drops-down from first priority swimline to "Issues without Epic" at the bottom of the page. It's very-very unplesant behabiour. Possible solutions: add "Epic link" to subtasks keep them under Epic swimline at least (regardless of the parent issue visibility)

            David Hübner added a comment -

            +1

            David Hübner added a comment - +1

            callum.smale added a comment -

            +1

            callum.smale added a comment - +1

            Oliver Febres-Cordero added a comment -

            Can you please review this ticket

            Oliver Febres-Cordero added a comment - Can you please review this ticket

              afb6234f8e80 Mark Patterson (Inactive)
              acardino Anna Cardino (Inactive)
              Affected customers:
              206 This affects my team
              Watchers:
              131 Start watching this issue

                Created:
                Updated:
                Resolved: