Uploaded image for project: 'Jira Platform Cloud'
  1. Jira Platform Cloud
  2. JRACLOUD-89106

Advanced Roadmaps Capacity Planning should show even distribution of workload

XMLWordPrintable

    • 0
    • 2

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      As a user, I would like to be able to see the workload evenly distributed amongst all iterations of a task. 

      Currently, Advanced Roadmaps linearly decreases the estimate for each iteration based on the team capacity and shows "all green" for each iteration, even though the workload overall is too much for the assigned team. Only in the last iteration it shows the actual overload.

      If the estimate was evenly spread amongst the timeline of the task, this would be immediately visible and measures could be taken more effectively, rather than checking on the last iteration of each task. This is eg. how BigPicture handles the capacity planning.

            [JRACLOUD-89106] Advanced Roadmaps Capacity Planning should show even distribution of workload

            Kate Durnell made changes -
            Component/s Original: Plan (Advanced Roadmaps) - Roadmap [ 61013 ]
            Component/s New: Plans - Timeline [ 77924 ]
            Key Original: JSWCLOUD-23210 New: JRACLOUD-89106
            Project Original: Jira Cloud [ 18511 ] New: Jira Platform Cloud [ 18514 ]
            Matthew Hunter made changes -
            Resolution New: Timed out [ 10 ]
            Status Original: Gathering Interest [ 11772 ] New: Closed [ 6 ]
            Matthew Hunter made changes -
            Labels New: cll-tf2202410

            Matthew Hunter added a comment -
            Atlassian Update - October 31, 2024

            Hi everyone,

            Thank you for bringing this suggestion to our attention. As explained in our new feature policy, there are many factors that influence our product roadmaps and determine the features we implement. When making decisions about what to prioritise and work on, we combine your feedback and suggestions with insights from our support teams, product analytics, research findings, and more. This information, combined with our medium- and long-term product and platform vision, determines what we implement and its priority order.

            Unfortunately, as a result of inactivity for an extended period of time, this suggestion didn’t make it to the roadmap and we are closing it.

            While this issue has been closed, our Product Managers continue to look at requests on jira.atlassian.com as they develop their roadmap, including closed ones. In addition, if you feel like this suggestion is still important to your team please let us know by commenting on this ticket.

            Thank you again for providing valuable feedback to our team - Jira Cloud Product Management

            Matthew Hunter added a comment - Atlassian Update - October 31, 2024 Hi everyone, Thank you for bringing this suggestion to our attention. As explained in our new feature policy , there are many factors that influence our product roadmaps and determine the features we implement. When making decisions about what to prioritise and work on, we combine your feedback and suggestions with insights from our support teams, product analytics, research findings, and more. This information, combined with our medium- and long-term product and platform vision, determines what we implement and its priority order. Unfortunately, as a result of inactivity for an extended period of time, this suggestion didn’t make it to the roadmap and we are closing it. While this issue has been closed, our Product Managers continue to look at requests on jira.atlassian.com as they develop their roadmap, including closed ones. In addition, if you feel like this suggestion is still important to your team please let us know by commenting on this ticket. Thank you again for providing valuable feedback to our team - Jira Cloud Product Management
            SET Analytics Bot made changes -
            Support reference count New: 2
            SET Analytics Bot made changes -
            UIS Original: 1 New: 0
            SET Analytics Bot made changes -
            UIS New: 1
            Mike Howells made changes -
            Workflow Original: JAC Suggestion Workflow JSWCLOUD [ 4285625 ] New: JAC Suggestion Workflow 3 [ 4367420 ]

            Karin.Gleichauf added a comment -

            When including regular meeting hours in our resource planning we need the ability to distribute the hours evenly over the complete project duration. Especially when auto-scheduling is used there should be the choice to distribute evenly vs "all meeting hours are pushed to the end".

            Karin.Gleichauf added a comment - When including regular meeting hours in our resource planning we need the ability to distribute the hours evenly over the complete project duration. Especially when auto-scheduling is used there should be the choice to distribute evenly vs "all meeting hours are pushed to the end".

            Chris Rosser added a comment -

            Agree this is the incorrect choice for the default behaviour. It's relatively easy to simulate "getting the task done really fast" by shortening the duration if workload is allocated evenly across the task.

            If workload is allocated unevenly stretching/shortening a task doesn't actually achieve anything as Jira has decided when the task should have finished based on the available capacity.

            This type of auto-scheduling functionality may be useful for some teams but absolutely should be part of autoscheduling and not the default behaviour.

            Chris Rosser added a comment - Agree this is the incorrect choice for the default behaviour. It's relatively easy to simulate "getting the task done really fast" by shortening the duration if workload is allocated evenly across the task. If workload is allocated unevenly stretching/shortening a task doesn't actually achieve anything as Jira has decided when the task should have finished based on the available capacity. This type of auto-scheduling functionality may be useful for some teams but absolutely should be part of autoscheduling and not the default behaviour.

              Unassigned Unassigned
              e5e7037d3158 Fabian Dengel
              Votes:
              9 Vote for this issue
              Watchers:
              8 Start watching this issue

                Created:
                Updated:
                Resolved: