Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-68632

Sub-Tasks do display within a Kanban board (documentation issue)

      Issue Summary

      Documentation is not accurate. Sub-tasks are displayed within a Kanban board.

      Environment

      *Jira 7.13
      *https://confluence.atlassian.com/jirasoftwareserver/monitoring-work-in-a-kanban-project-938845480.html#MonitoringworkinaKanbanproject-AbouttheKanbanboard

      Steps to Reproduce

      1. Create Kanban board.
      2. Create Issue.
      3. Create sub-task to your issue.
      4. It will now display within the board.

      Expected Results

      Sub-task should not display as documentation says the following:

      An issue will only be visible in the Kanban board if: 

      • the issue is not a sub-task,

      Actual Results

      Sub-task is displayed within the Kanban board.

      Notes

      (Optional - If Necessary)

      Workaround

      None.

            [JRASERVER-68632] Sub-Tasks do display within a Kanban board (documentation issue)

            Aakrity Tibrewal made changes -
            Resolution New: Low Engagement [ 10300 ]
            Status Original: Gathering Impact [ 12072 ] New: Closed [ 6 ]
            Aakrity Tibrewal made changes -
            Labels Original: documentation New: cleanup-seos-fy25 documentation

            Atlassian Update - 10 April 2025

            Hi,

            At Atlassian, our goal is to ensure we’re providing the best experience for our customers. With our new Data Center strategy, Atlassian's focus is on security, compliance, and performance and is a key driver in prioritizing bugs. Closing the bugs that do not fall into those categories will allow us to focus on the ones in the most current versions of our products.

            This bug is being closed due to a lack of engagement in the last four years, including no new watchers, votes, or comments; this inactivity suggests a low impact.

            Please note the comments on this thread are not being monitored.

            You can read more about our bug fix policy here and how we prioritize bugs.

            To learn more about our recent investments in Jira Data Center, please check our public roadmap and dashboards containing recently resolved issues, current work, and future plans.

            Kind regards,
            Jira Data Center

            Aakrity Tibrewal added a comment - Atlassian Update - 10 April 2025 Hi, At Atlassian, our goal is to ensure we’re providing the best experience for our customers. With our new Data Center strategy, Atlassian's focus is on security, compliance, and performance and is a key driver in prioritizing bugs. Closing the bugs that do not fall into those categories will allow us to focus on the ones in the most current versions of our products. This bug is being closed due to a lack of engagement in the last four years , including no new watchers, votes, or comments; this inactivity suggests a low impact. Please note the comments on this thread are not being monitored. You can read more about our bug fix policy here and how we prioritize bugs. To learn more about our recent investments in Jira Data Center, please check our public roadmap and dashboards containing recently resolved issues , current work, and future plans . Kind regards, Jira Data Center
            Bugfix Automation Bot made changes -
            Minimum Version New: 7.13
            Mateusz Marzęcki made changes -
            Occurrence Factor New: 25% [ 12831 ]
            Mateusz Marzęcki made changes -
            Status Original: Needs Triage [ 10030 ] New: Gathering Impact [ 12072 ]
            Mateusz Marzęcki made changes -
            Labels New: documentation
            Stephen Sifers made changes -
            Attachment New: screenshot-1.png [ 337763 ]
            Stephen Sifers created issue -

              Unassigned Unassigned
              ssifers@atlassian.com Stephen Sifers
              Affected customers:
              0 This affects my team
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: