• 1
    • 6
    • Hide
      Atlassian Status as at 13 November 2015

      Thanks for your feedback and comments, the JIRA Agile team is working hard to improve the product and we are aware of the many requests here on jira.atlassian.com

      Details of issues currently in development or recently shipped are noted in comment-825508.

      We understand that this is a significant issue for many of you. In the comments below there are some workarounds and links to add-ons in the Atlassian Marketplace that may be of assistance.

      We cannot provide any guidance at this time as to when this Suggestion will be addressed.

      Kind regards,
      Martin
      JIRA Software

      Show
      Atlassian Status as at 13 November 2015 Thanks for your feedback and comments, the JIRA Agile team is working hard to improve the product and we are aware of the many requests here on jira.atlassian.com Details of issues currently in development or recently shipped are noted in comment-825508 . We understand that this is a significant issue for many of you. In the comments below there are some workarounds and links to add-ons in the Atlassian Marketplace that may be of assistance. We cannot provide any guidance at this time as to when this Suggestion will be addressed. Kind regards, Martin JIRA Software
    • 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.

      As a Greenhopper Scrum product owner, I want story estimates to automatically total to the sum of the estimates for all sub-tasks IF and ONLY IF subtasks are entered (else I want story estimates to be manual entry) so that I can view on the scrum board the original estimate against the remaining time.

      Definition of Done:
      1) When no sub-tasks exist for a story, the estimate field for the story allows entry of a value manually
      2) When one or more sub-tasks exist for a story, the estimate field for the story is calculated as the sum of the estimates for all sub-tasks for that story

      Context:

      I'm finding a feature in Greenhopper to NOT operate as I would have expected. The feature is in estimating where the estimation on the scrum board is configured for original time estimates. What I would like is:
      1) when no sub-tasks are created for a story, the estimation and remaining fields are editable within the story
      2) when sub-tasks have been created, the story estimate and remaining fields are calculated as the sum of the estimate and remaining fields for the sub-tasks

      What's currently happening is that the story estimate field is not calculated from the sum of the sub-tasks but the story remaining field is. Worse, if you enter a value in the story estimate field when sub-tasks have been added and estimated, the value entered into the story estimate field is added to the story remaining field, which already has the sum of the sub-tasks. Thus, if, as a work around, you try to manually enter a story estimate that equals the sum of the sub-task estimates, the story remaining field value doubles. There's no work around for this. This feature seems poorly defined. I understand what the product team was trying to accomplish... the ability to estimate and view remaining values for stories that have no sub-tasks or prior to sub-tasks being added. What they missed is that the field could serve both functions - manual entry when no sub-tasks exist and calculated value when sub-tasks do exist. I strongly urge the product team to consider this feature at their earliest opportunity as the inability to see from the scrum board the original estimate against the remaining value in plan and work mode is a problem.

      Steps to reproduce
      1. Configure Scrum board to use "Original Time Estimate" for Estimation Statistic
      2. Configure Scrum board to use "Remaining Estimate and Time Spent" for Time Tracking
      3. Create an issue with issue type Story, without specifying any Original Estimate and Remaining Estimate
      4. Create 2 sub-tasks for this issue.
        • Sub-task 1 has Remaining Estimate of 4 hours
        • Sub-task 2 has Remaining Estimate of 2 hours
      5. Checking parent of sub-tasks in Issue View, Original Estimate and Remaining Estimate is now shown as 6 hours
      6. Navigate back to Scrum board, open Issue Detail View, and Original Estimate for parent issue is Unestimated

        1. Automatic Story Estimation.png
          Automatic Story Estimation.png
          20 kB
        2. Bildschirmfoto 2015-05-07 um 11.33.21.png
          Bildschirmfoto 2015-05-07 um 11.33.21.png
          29 kB
        3. Not on board.png
          Not on board.png
          5 kB
        4. ScreenHunter_02 Oct. 07 09.30.gif
          ScreenHunter_02 Oct. 07 09.30.gif
          4 kB
        5. screenshot-1.png
          screenshot-1.png
          41 kB
        6. sprint-plan.png
          sprint-plan.png
          29 kB
        7. sprint-report.png
          sprint-report.png
          66 kB
        8. Stupid Scrum Board.png
          Stupid Scrum Board.png
          119 kB
        9. velocity.png
          velocity.png
          6 kB

            [JSWSERVER-13138] Sum estimates from sub-tasks in user stories

            HI,

            I have 2 projects and in that one project e have created stories,after speint planning we added suntasks and provided orinal efforts and remainig efforts and all the subtasks totals(Originala nd Remaining estimates) are  showing at partent story.

            also in another project we have created stories and provided original estimates and Remaining estimates at story level.

            now i am creating custom charts for original estimates,Remaining estimates and Time spent but not showing Original estimates for stories added with subtasks and showing original estimate for stories which are not having subtasks.

            also for time spent - i am using sum time spent filed in custom chart and getting the time in secons but i need in hours or days

            also for remaining estimates - i am using total remaining estimates label in custom chart and getting estimates in hours but not displayed in lable

            so here i need some hlep on this how i can get all these 3 values in custom charts for all user stories with subtaks and with our subtasks

             

            I need help on custom charts to fetch Original estimate,remainig estimate and time spent

            Krishna Reddy added a comment - HI, I have 2 projects and in that one project e have created stories,after speint planning we added suntasks and provided orinal efforts and remainig efforts and all the subtasks totals(Originala nd Remaining estimates) are  showing at partent story. also in another project we have created stories and provided original estimates and Remaining estimates at story level. now i am creating custom charts for original estimates,Remaining estimates and Time spent but not showing Original estimates for stories added with subtasks and showing original estimate for stories which are not having subtasks. also for time spent - i am using sum time spent filed in custom chart and getting the time in secons but i need in hours or days also for remaining estimates - i am using total remaining estimates label in custom chart and getting estimates in hours but not displayed in lable so here i need some hlep on this how i can get all these 3 values in custom charts for all user stories with subtaks and with our subtasks   I need help on custom charts to fetch Original estimate,remainig estimate and time spent

            Yeah ideally there shouldn't be an 'Original Estimate' for the user story as the User Story would have 'Story Points' to depict complexity.

            The 'Original Estimates' of the sub-tasks should add and roll up to the parent user story.

            Because any work done to achieve DoD on a user story should be part of a sub-task imo.

            farhan.javed added a comment - Yeah ideally there shouldn't be an 'Original Estimate' for the user story as the User Story would have 'Story Points' to depict complexity. The 'Original Estimates' of the sub-tasks should add and roll up to the parent user story. Because any work done to achieve DoD on a user story should be part of a sub-task imo.

            A highly recommended functionality to achieve as it saves from manually entered error prone values. 

            • A simple scenario is that a user story is created by the Product Owner.
              • Then a developer creates five tasks and estimates them along with the team in the sprint planning meeting.
                • The sum of these estimates to the five tasks should be the actual sum of the user story.
                • When there are more tasks created for the user story, and the tasks are estimated it should update the estimate of the user story accordingly

            Muneer Ahmed added a comment - A highly recommended functionality to achieve as it saves from manually entered error prone values.  A simple scenario is that a user story is created by the Product Owner. Then a developer creates five tasks and estimates them along with the team in the sprint planning meeting. The sum of these estimates to the five tasks should be the actual sum of the user story. When there are more tasks created for the user story, and the tasks are estimated it should update the estimate of the user story accordingly

            This is a much needed functionality.

            jiraruna@runa.ru added a comment - This is a much needed functionality.

            same here

            Kai Macmaster added a comment - same here

            same problem, quite annoying issue..

            Artem Markov added a comment - same problem, quite annoying issue..

            This works in old view - I finally caved and switched to the new view because enough colleagues use it that I couldn't be useful to them by having a different layout. Now there's no sum of sub-task estimates on stories, either in the issue detail view on the sprint board or when you look at the ticket itself and there does not seem to be an option to add the field. The closest I got was adding it to the tickets on the board. I don't see the benefit of taking options away from users unless they actually cause problems. The benefit of Jira over other systems is that, while it's not simple, it is also not opinionated and users can customise how they use it. This kind of change makes me want to pay more attention to those voices (of which there are always many) who want us to transition to a simpler software, since the customisation that I always promote about Jira is being taken away piece by piece.

            Emmanuel Valentine added a comment - This works in old view - I finally caved and switched to the new view because enough colleagues use it that I couldn't be useful to them by having a different layout. Now there's no sum of sub-task estimates on stories, either in the issue detail view on the sprint board or when you look at the ticket itself and there does not seem to be an option to add the field. The closest I got was adding it to the tickets on the board. I don't see the benefit of taking options away from users unless they actually cause problems. The benefit of Jira over other systems is that, while it's not simple, it is also not opinionated and users can customise how they use it. This kind of change makes me want to pay more attention to those voices (of which there are always many) who want us to transition to a simpler software, since the customisation that I always promote about Jira is being taken away piece by piece.

            Hi, I couldn't agree more that Jira has actually shown the total subtask estimates on the Stories view. However, we just need it to be shown on the Board as well. Hope it's not rocket science to do so. Cheers

            vicky.santosa added a comment - Hi, I couldn't agree more that Jira has actually shown the total subtask estimates on the Stories view. However, we just need it to be shown on the Board as well. Hope it's not rocket science to do so. Cheers

            Magnus Boje Marcussen added a comment - - edited

            Hi. This is a dealbreaker for us. Our User Stories requires several specialists who needs to estimate on sub-tasks. I simply cannot understand why this is not a feature. It seems like the most basic option to have in a Agile tool like this. Our organisation dictates the use of Jira, so unfortunately we have no other option. In my head this should qualify as a bug. So please fix this.  /magnus

            Magnus Boje Marcussen added a comment - - edited Hi. This is a dealbreaker for us. Our User Stories requires several specialists who needs to estimate on sub-tasks. I simply cannot understand why this is not a feature. It seems like the most basic option to have in a Agile tool like this. Our organisation dictates the use of Jira, so unfortunately we have no other option. In my head this should qualify as a bug. So please fix this.  /magnus

            Hi! I was extremely surprised it doesn't work in Jira. When does it possible to solve this bug?

            Alex Litvinov added a comment - Hi! I was extremely surprised it doesn't work in Jira. When does it possible to solve this bug?

              Unassigned Unassigned
              5e9964367bf7 Richa Raghuvanshi
              Votes:
              74 Vote for this issue
              Watchers:
              45 Start watching this issue

                Created:
                Updated: