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

As a rapid board user, able to rank sub-task in Plan mode

XMLWordPrintable

    • 1
    • 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.

      The prioritization of sub-task in Issue view page would not reflect the ranking of sub-task in GreenHopper as it uses the ranking instead. Thus, it would be great if ranking the sub-tasks within the parent issue/story is possible in the Plan mode. The work would be less efficient if the sub-tasks are able to be ranked in Work mode.

      Lets assume that there are 10 stories inside the sprint and each of the stories has 10 sub-tasks to be ranked. It isn't an efficient way to work where you would require to plan twice: once in during the Plan mode for the stories, and another during the work mode for the sub-tasks.

            [JSWSERVER-7467] As a rapid board user, able to rank sub-task in Plan mode

            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

            Hector Herrera added a comment -

            I agree with SYSGO AG... being able to rank subtasks is a need...when we are planning, we determine a specific order for the tasks to perform for the completion of a story. For example, we may first need to analyze data, setup certain configurations or code, then design, develop, test, document, etc.

            Hector Herrera added a comment - I agree with SYSGO AG... being able to rank subtasks is a need...when we are planning, we determine a specific order for the tasks to perform for the completion of a story. For example, we may first need to analyze data, setup certain configurations or code, then design, develop, test, document, etc.

            SYSGO GmbH added a comment -

            For our work planning, it is crucial to rank the technical tasks in a story.

            Without this, the engineers will work down the tasks in a less efficient order.

            In the classic planning board, the technical tasks could be shown or hidden by a board button "Hide Sub-Tasks". This allowed to plan the tasks within the story.

            This is strongly required.

            SYSGO GmbH added a comment - For our work planning, it is crucial to rank the technical tasks in a story. Without this, the engineers will work down the tasks in a less efficient order. In the classic planning board, the technical tasks could be shown or hidden by a board button "Hide Sub-Tasks". This allowed to plan the tasks within the story. This is strongly required.

              Unassigned Unassigned
              znoorsazali Zul NS [Atlassian]
              Votes:
              9 Vote for this issue
              Watchers:
              9 Start watching this issue

                Created:
                Updated:
                Resolved: