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

Sum of remaining estimate on sub-tasks not displayed on user story in agile boards

XMLWordPrintable

    • 8
    • 25
    • Hide
      Atlassian Status as at 15 February 2018

      Hi everyone,

      Thanks for your interest in this issue.
      This request is considered a potential addition to our longer-term roadmap.

      We'll typically review this request in about 12 months time, at which point we’ll consider whether we need to alter its status.

      For the nearest future we've decided to prioritize other areas of the Jira Server roadmap, including:

      • Performance and stability improvements
      • Archiving projects for improved performance
      • Optimising the use of custom fields
      • Improving performance of boards
      • Improving Jira notifications
      • Allowing users to edit shared filters and dashboards
      • Mobile app for Jira Server

      You can learn more about our approach to highly voted server suggestions here.

      To learn more on how JAC suggestions are reviewed, see our updated workflow for server feature suggestions.

      Kind regards,

      Jira Server Product Management

      Show
      Atlassian Status as at 15 February 2018 Hi everyone, Thanks for your interest in this issue. This request is considered a potential addition to our longer-term roadmap. We'll typically review this request in about 12 months time, at which point we’ll consider whether we need to alter its status. For the nearest future we've decided to prioritize other areas of the Jira Server roadmap, including: Performance and stability improvements Archiving projects for improved performance Optimising the use of custom fields Improving performance of boards Improving Jira notifications Allowing users to edit shared filters and dashboards Mobile app for Jira Server You can learn more about our approach to highly voted server suggestions here . To learn more on how JAC suggestions are reviewed, see our updated workflow for server feature suggestions . Kind regards, Jira Server Product Management
    • 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.

      NOTE: This suggestion is for JIRA Software Server. Using JIRA Software Cloud? See the corresponding suggestion.

      Hi

      I would like to start using the agile board but I have the problem that we estimate all the hours on sub-tasks and not on the user story itself. So the needed work should be always the sum of estimates on sub-tasks.

      But as you can see on the two attached screenshot, the displayed estimation is 0h instead of 3d 5h 30m.

      Could you please fix that? As I could see in other bug reports, this problem has already been fixed once, but it is there again.

      Thanks & cheers
      Martin

        1. 21-02-2013 09-51-30.png
          53 kB
          Martin Zeltner
        2. 21-02-2013 10-15-52.png
          185 kB
          Martin Zeltner
        3. existing1.png
          20 kB
          Martin
        4. proposal1.png
          20 kB
          Martin
        5. 6.1.1 Plan.png
          20 kB
          Sarah Prouse
        6. 6.1.1 Work.png
          31 kB
          Sarah Prouse
        7. 6.1.1 Estimation.png
          27 kB
          Sarah Prouse
        8. with-card-layout.png
          85 kB
          Martin
        9. without-card-layout.png
          75 kB
          Martin

            [JSWSERVER-7719] Sum of remaining estimate on sub-tasks not displayed on user story in agile boards

            Rebeca Cunningham added a comment -

            +1

            Rebeca Cunningham added a comment - +1

            Trinh Nguyen added a comment -

            Is there any update on this? We also need this feature...

            Trinh Nguyen added a comment - Is there any update on this? We also need this feature...

            Thomas Müller added a comment -

            My team cannot understand that this basic function is not being implemented.

            Thomas Müller added a comment - My team cannot understand that this basic function is not being implemented.

            Artem Markov added a comment -

            the earliest request about this feature I have found so far is dated 2014... shorter time to market with agile they said)))

            Artem Markov added a comment - the earliest request about this feature I have found so far is dated 2014... shorter time to market with agile they said)))

            Juan Manuel Antonellini added a comment -

            Is there a reason why this is not implemented yet? Waiting for this to happen..

            Juan Manuel Antonellini added a comment - Is there a reason why this is not implemented yet? Waiting for this to happen..

            Mikalai Karol added a comment -

            My team is still waiting for this feature...

            Mikalai Karol added a comment - My team is still waiting for this feature...

            Michael Daoust added a comment -

            My teams write a story and we add subtasks to reflect the actual work and we estimate effort on each subtask to find the total effort of the story.

            Other competitors have this functionality already and have had it for quite a long time. 

             

            Michael Daoust added a comment - My teams write a story and we add subtasks to reflect the actual work and we estimate effort on each subtask to find the total effort of the story. Other competitors have this functionality already and have had it for quite a long time.   

            Luke Hanson added a comment -

            Voting and commenting on these issues it totally futile, even providing feedback directly to Jira's "Product Managers" has no effect.

            I've had to implement a process workaround to cater for Atlassians failure to address a fundamental BUG in their system.

            This has been set to future consideration in approx. 12 months time, this has been around for 5 Years plus! we have to get into the delorean to even remember when it was raised. 

            You've said you've decided to focus on other priorities, around performance and stability - theses issues are YOUR issues as the supplier of the product, you shouldn't be penalizing your customers for your lack of maintenance and upkeep of YOUR product - whilst also increasing your pricing using the excuse that you need more money to keep developing Features!?!?!? WHAT FEATURES?!?!? maintenance of YOUR product is not a Feature! 

             

             

            Luke Hanson added a comment - Voting and commenting on these issues it totally futile, even providing feedback directly to Jira's "Product Managers" has no effect. I've had to implement a process workaround to cater for Atlassians failure to address a fundamental BUG in their system. This has been set to future consideration in approx. 12 months time, this has been around for 5 Years plus! we have to get into the delorean to even remember when it was raised.  You've said you've decided to focus on other priorities, around performance and stability - theses issues are YOUR issues as the supplier of the product, you shouldn't be penalizing your customers for your lack of maintenance and upkeep of YOUR product - whilst also increasing your pricing using the excuse that you need more money to keep developing Features!?!?!? WHAT FEATURES?!?!? maintenance of YOUR product is not a Feature!     

            Mike Buscemi added a comment -

            436 votes and over 100 comments..what is it going to take to get this bug fixed Atlassian?!? 

            Dave Ingram's comment from 09/Jan/2018 8:32 PM: sums it up perfectly:

             

            "If Story has no sub-tasks make Points on Story = Points on Story (manually edit, as now)

            else

            If Story has sub-tasks make Points on Story = Sum of all Points on Sub-Tasks (automate it, or maybe add a button to allow user to 'recalculate' if they wish. Button can go 'red' of sub-tasks sum of points on sub-tasks doesn't agree with points on Story.

            Coupled with this, it would be great to see Story Points on Sub-Tasks contribute to the Burndown, whereas at present, burndown is unaffected when sub-tasks are DONE, and only changes when patent STORY is DONE."

             

            Please listen to your peeps Atlassian!

             

             

            Mike Buscemi added a comment - 436 votes and over 100 comments..what is it going to take to get this bug fixed Atlassian?!?  Dave Ingram's comment from 09/Jan/2018 8:32 PM: sums it up perfectly:   "If Story has no sub-tasks make Points on Story = Points on Story (manually edit, as now) else If Story has sub-tasks make Points on Story = Sum of all Points on Sub-Tasks (automate it, or maybe add a button to allow user to 'recalculate' if they wish. Button can go 'red' of sub-tasks sum of points on sub-tasks doesn't agree with points on Story. Coupled with this, it would be great to see Story Points on Sub-Tasks contribute to the Burndown, whereas at present, burndown is unaffected when sub-tasks are DONE, and only changes when patent STORY is DONE."   Please listen to your peeps Atlassian!    

            Michael Griebling added a comment - - edited

            @jokerdenkazantsev1893399938 Just curious what software you moved to?

            Michael Griebling added a comment - - edited @ jokerdenkazantsev1893399938 Just curious what software you moved to?

              Unassigned Unassigned
              5b5e9042805e Martin Zeltner
              Votes:
              513 Vote for this issue
              Watchers:
              258 Start watching this issue

                Created:
                Updated: