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

As a user, I'd like to be able to access sub-tasks in sprint planning mode on rapid board

XMLWordPrintable

    • 0
    • 2
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      Please allow the ability to manage and view sub-task from the sprint planning mode rapid board view. Sometimes it is required to split up work from a larger project and only account for a portion of the sub-task in a particular sprint. For that reason we need the ability to manage task and sub-task in the planning mode to ensure required issues are not accidentally left behind.

          Form Name

            [JSWSERVER-8802] As a user, I'd like to be able to access sub-tasks in sprint planning mode on rapid board

            Aakrity Tibrewal added a comment -
            Atlassian Update - 24 March 2025

            Hello,

            Thank you for submitting this suggestion. We appreciate you taking the time to share your ideas for improving our products, as many features and functions come from valued customers such as yourself.

            Atlassian is committed to enhancing the security and compliance of our Data Center products, with an emphasis on sustainable scalability and improving the product experience for both administrators and end-users. We periodically review older suggestions to ensure we're focusing on the most relevant feedback. This suggestion 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. Therefore, this suggestion is not in consideration for our future roadmap.

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

            You can read more about our approach to highly voted suggestions here and how we prioritize what to implement here.

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

            Kind regards,
            Jira Data Center

            Aakrity Tibrewal added a comment - Atlassian Update - 24 March 2025 Hello, Thank you for submitting this suggestion. We appreciate you taking the time to share your ideas for improving our products, as many features and functions come from valued customers such as yourself. Atlassian is committed to enhancing the security and compliance of our Data Center products, with an emphasis on sustainable scalability and improving the product experience for both administrators and end-users. We periodically review older suggestions to ensure we're focusing on the most relevant feedback. This suggestion 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. Therefore, this suggestion is not in consideration for our future roadmap. Please note the comments on this thread are not being monitored. You can read more about our approach to highly voted suggestions here and how we prioritize what to implement here. To learn more about our recent investments in Jira Data Center, please check our public roadmap and our dashboards, which contain recently resolved issues , current work, and future plans. Kind regards, Jira Data Center

            Renato Miranda added a comment -

            Atlassians, despite the low number of votes for this issues, you should take in account the huge number of discussions around this matter and get this issue prioritized. I am sure JIRA would reconquer old fans... I hope someone (not a bot) read this. :o)

            Renato Miranda added a comment - Atlassians, despite the low number of votes for this issues, you should take in account the huge number of discussions around this matter and get this issue prioritized. I am sure JIRA would reconquer old fans... I hope someone (not a bot) read this. :o)

            Jared Wyatt added a comment -

            see: https://confluence.atlassian.com/pages/viewpage.action?pageId=394465595

            Displaying sub-tasks under parent tasks in the planning board was a capability in the now-deprecated classic boards. Why is it taking so long to implement this for the planning mode in rapid boards?

            Please prioritize this. It's a massive pain point in our sprint planning.

            Jared Wyatt added a comment - see: https://confluence.atlassian.com/pages/viewpage.action?pageId=394465595 Displaying sub-tasks under parent tasks in the planning board was a capability in the now-deprecated classic boards. Why is it taking so long to implement this for the planning mode in rapid boards? Please prioritize this. It's a massive pain point in our sprint planning.

            Hans-Jürgen Tappe added a comment -

            Not only does the ranking of the tasks within a story have impact on the order they are worked down and thus the efficiency in which work is performed. Also, we need to see at a glance, which stories do not have any sub-tasks defined, so we can communicate with the team to define tasks for the stories.
            We do not necessarily need to put the stora and it's tasks into different versions or sprints, but we need the transparency to see the actually planned work (i.e. including the sub-tasks). We can live with the fact (as defined in Scrum) that a story which is not completed, will just be moved to the next sprint.

            Hans-Jürgen Tappe added a comment - Not only does the ranking of the tasks within a story have impact on the order they are worked down and thus the efficiency in which work is performed. Also, we need to see at a glance, which stories do not have any sub-tasks defined, so we can communicate with the team to define tasks for the stories. We do not necessarily need to put the stora and it's tasks into different versions or sprints, but we need the transparency to see the actually planned work (i.e. including the sub-tasks). We can live with the fact (as defined in Scrum) that a story which is not completed, will just be moved to the next sprint.

            Sorin Sbarnea added a comment -

            Yes, we had to find very ugly workarounds due to this limitation. For example one would assume that you could create a sub-task for development work and one for QA work needed for the item to be finished. But if you are doing this you will not be able to plan these sub-tasks using SCRUM.

            Sorin Sbarnea added a comment - Yes, we had to find very ugly workarounds due to this limitation. For example one would assume that you could create a sub-task for development work and one for QA work needed for the item to be finished. But if you are doing this you will not be able to plan these sub-tasks using SCRUM.

            Larry Becker added a comment -

            The key piece that is hindering the use of the sub-task is not being able to see them in the backlog when planning out a particular sprint. You have to click on a particular epic in order to see or search for issues in the backlog vs being able to search for them out of the larger queue and adding them section by section when needed.

            Larry Becker added a comment - The key piece that is hindering the use of the sub-task is not being able to see them in the backlog when planning out a particular sprint. You have to click on a particular epic in order to see or search for issues in the backlog vs being able to search for them out of the larger queue and adding them section by section when needed.

              Unassigned Unassigned
              cgauterio Clarissa Gauterio (Inactive)
              Votes:
              26 Vote for this issue
              Watchers:
              15 Start watching this issue

                Created:
                Updated:
                Resolved: