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

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

    XMLWordPrintable

    Details

    • Introduced in Version:
      6.03
    • Support reference count:
      9
    • Symptom Severity:
      Severity 3 - Minor
    • UIS:
      10
    • Current Status:
      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

      Description

      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.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              acardino Anna Cardino (Inactive)
              Votes:
              132 Vote for this issue
              Watchers:
              90 Start watching this issue

                Dates

                Created:
                Updated: