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

Would like to see sub-tasks estimation in the main task on the Plan Mode of the Rapid Board

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

      It would be a great improvement if we could see the Sub-tasks Estimation in main task on the Plan Mode of the Rapid Board.

      Currently, we are only able to see the main issue estimation, and if we only add estimations to the sub-tasks, no estimations are displayed are all.

            [JSWSERVER-5614] Would like to see sub-tasks estimation in the main task on the Plan Mode of the Rapid Board

            Jo added a comment -

            Any update on this one? the feature would be great!

            Jo added a comment - Any update on this one? the feature would be great!

            Hi, it is a functionality we are interested in using too.

            Can you please let us know something about this topic?

            Davide Barro added a comment - Hi, it is a functionality we are interested in using too. Can you please let us know something about this topic?

            rossy89 added a comment -

            This is much needed functionality for my team as well!!! Otherwize, we cannot use the sub-tasks with their whole value as finally the time estimate is to accumulated into the parent task. 

            rossy89 added a comment - This is much needed functionality for my team as well!!! Otherwize, we cannot use the sub-tasks with their whole value as finally the time estimate is to accumulated into the parent task. 

            This is a much needed functionality.

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

            dforson added a comment -

            Yes please add this feature ASAP. Doesn't make any sense not to have it.

            thanks.

            dforson added a comment - Yes please add this feature ASAP. Doesn't make any sense not to have it. thanks.

            Aditi Sharma added a comment - - edited

            This ticket was created in 2012 (launch year of Jira in the Atlassian Marketplace??) and so many people aka "Jira users/Atlassian customers" have been asking for this feature since then and still the status of the issue is "This suggestion needs more unique domain votes and comments before being reviewed by our teams".

            Apparently more people have asked for the smilies in Jira than this issue?  Interesting ROI

            It is frustrating and surprising that it has not been escalated to Mike Cannon-Brookers and Scott Farquhar yet! 

            Aditi Sharma added a comment - - edited This ticket was created in 2012 (launch year of Jira in the Atlassian Marketplace??) and so many people aka "Jira users/Atlassian customers" have been asking for this feature since then and still the status of the issue is "This suggestion needs more unique domain votes and comments before being reviewed by our teams". Apparently more people have asked for the smilies in Jira than this issue?   Interesting ROI It is frustrating and surprising that it has not been escalated to Mike Cannon-Brookers and Scott Farquhar yet! 

            +1

            YES YES YES. This is so frustrating, why would subtasks have points at all if they aren't going to count towards burndown or have any use really?!  

            Jamie Gerace added a comment - YES YES YES. This is so frustrating, why would subtasks have points at all if they aren't going to count towards burndown or have any use really?!  

            Want this, please.

            Michael Blanchard added a comment - Want this, please.

            This functionality makes much of the reporting and or features not effective. I customized some field usage and built my own reports. I may end up just building my own PM app.

            James Anderson added a comment - This functionality makes much of the reporting and or features not effective. I customized some field usage and built my own reports. I may end up just building my own PM app.

            6 years and still counting. I never thought this would take this long to be decided... 
            Meanwhile there is a workaround using scriptrunner. It works, not perfectly but better than the current state, which is just useless:
            https://riada.se/estimate-your-sub-tasks-in-jira-agile/

             

            Carl-Marcus Scheffler added a comment - 6 years and still counting. I never thought this would take this long to be decided...  Meanwhile there is a workaround using scriptrunner. It works, not perfectly but better than the current state, which is just useless: https://riada.se/estimate-your-sub-tasks-in-jira-agile/  

            If Atlassian would be as funny as they were back in the days, they would have posted an answer like: https://www.youtube.com/watch?v=JIuYQ_4TcXg

             

            this issue is still open after ~6yrs without a clear statement why this issue isn't solved / isn't considered to be an issue or whatsoever ... there are several scenarios where it's proofen that it simply doesn't work, but what can we do?

             

            I don't think, that things will change ... lost a bit of the excitement about Atlassian toolset - since it's not the only issue which is describing a terrible situation, without any reaction

            Jürgen Kajdocsy added a comment - If Atlassian would be as funny as they were back in the days, they would have posted an answer like: https://www.youtube.com/watch?v=JIuYQ_4TcXg   this issue is still open after ~6yrs without a clear statement why this issue isn't solved / isn't considered to be an issue or whatsoever ... there are several scenarios where it's proofen that it simply doesn't work, but what can we do?   I don't think, that things will change ... lost a bit of the excitement about Atlassian toolset - since it's not the only issue which is describing a terrible situation, without any reaction

            @gwidener thanks for the info. From what version of Jira did the total start to appear in the board?

            Francesco Balestrieri added a comment - @gwidener thanks for the info. From what version of Jira did the total start to appear in the board?

            +1 Would love to see this feature supported for my company workflow

            Steve Judkins added a comment - +1 Would love to see this feature supported for my company workflow

            the total of subtasks now appears on the task board main item, but the individual estimates aren't visible in the subtask list.  Still makes me want to not use subtasks  -even though it's the right thing to do.

             

             

            Glenn Widener added a comment - the total of subtasks now appears on the task board main item, but the individual estimates aren't visible in the subtask list.  Still makes me want to not use subtasks  -even though it's the right thing to do.    

            +1 vote. For the second time in my life I'm working at a company where we will abandon sub-tasks because Atlassians can't be bothered to sum some numbers in a way that any sane person would expect. 

            Rutger Schaafsma added a comment - +1 vote. For the second time in my life I'm working at a company where we will abandon sub-tasks because Atlassians can't be bothered to sum some numbers in a way that any sane person would expect. 

            +1 How many votes to get this on the road map?

            Samson Williams added a comment - +1 How many votes to get this on the road map?

            +1

            planning without this feature is a nightmare

            Andrey Zabaev added a comment - +1 planning without this feature is a nightmare

            also need this feature

            Yurii Bondarenko added a comment - also need this feature

            Please implement this asap !

            Grzegorz Zuber added a comment - Please implement this asap !

            +1

            Stas Bichenko added a comment - +1

            +1

            +1

            Andreu Harris added a comment - +1

            +1

            Mitchel Meijer added a comment - +1

            +1

            Luke Carpenter added a comment - +1

            +1

            Agnes Fodor added a comment - +1

            +1 again, although we've given up on this, since this issue is open since 2012, and there is no indication of this moving forward

            I was angry at Atlassian at first, now I'm just sad

            If anything, Atlassian has shown that it's become too big and slow to implement valuable functionalities, so it might make sense to start looking for a alternate solution or develop our own project management tool.

            Tomislav Šantek added a comment - +1 again, although we've given up on this, since this issue is open since 2012, and there is no indication of this moving forward I was angry at Atlassian at first, now I'm just sad If anything, Atlassian has shown that it's become too big and slow to implement valuable functionalities, so it might make sense to start looking for a alternate solution or develop our own project management tool.

            +1 

             

            This is very critical issue for our organization. Please fix this issue.

            NehaNagori added a comment - +1    This is very critical issue for our organization. Please fix this issue.

            +1

            Alok Chandna added a comment - +1

            +1

            +1

            David Nason added a comment - +1

            +1

            Grzegorz Judas added a comment - +1

            +1

            Justin Parmar added a comment - +1

            Liron Keren added a comment - - edited

            fact is that user story estimation are being displayed correctly if entered manually but will not get displayed if left to be auto calculated by the system (only displayed if the user story issues are opened outside of the backlog/sprint/board view)
            Do not understand this hesitation to properly display and summarise the numbers while they are currently being displayed and summarised wrongly. Does someone in Atlassian really think that a support ticket will be opened to complain about a correct calculation and display of user stories ?!?!?

            Liron Keren added a comment - - edited fact is that user story estimation are being displayed correctly if entered manually but will not get displayed if left to be auto calculated by the system (only displayed if the user story issues are opened outside of the backlog/sprint/board view) Do not understand this hesitation to properly display and summarise the numbers while they are currently being displayed and summarised wrongly. Does someone in Atlassian really think that a support ticket will be opened to complain about a correct calculation and display of user stories ?!?!?

            exadannyd added a comment -

            +1

            exadannyd added a comment - +1

            +10086

            alex-magebinary added a comment - +10086

            +1

            Angela Surkau added a comment - +1

            +1

            Matt Comstock added a comment - +1

            +1

            Viktor Sterner added a comment - +1

            Michael added a comment - - edited

            I agree with @Lawrence Lachman. We have to do the same thing. I still can't believe that 3.5 years later this issue has not been resolved. This should have been one of your top priority work items and fixed a long time ago. You (JIRA) give us the ability to break out a story into subtasks and estimate those subtasks, but yet you do not roll up the estimates on the planning board which again makes it useless for product owners such as myself. Please tell me how that makes sense. I would like to know how others are getting around this and planning their sprints without seeing the estimates. This makes it very time consuming and costly to our organization. This needs to be fixed ASAP!

            Michael added a comment - - edited I agree with @Lawrence Lachman. We have to do the same thing. I still can't believe that 3.5 years later this issue has not been resolved. This should have been one of your top priority work items and fixed a long time ago. You (JIRA) give us the ability to break out a story into subtasks and estimate those subtasks, but yet you do not roll up the estimates on the planning board which again makes it useless for product owners such as myself. Please tell me how that makes sense. I would like to know how others are getting around this and planning their sprints without seeing the estimates. This makes it very time consuming and costly to our organization. This needs to be fixed ASAP!

            Without the visibility of the sub-task estimation in the plan mode, we have to resort to manually going to each parent issue and adding the sub-task estimations up with a calculator and keeping a separate table - outside of JIRA - that tracks how many hours have been assigned to each team member versus their capacity for the sprint. This is ridiculous. It truly makes the plan mode worthless to us because it does not help us do any planning at all.

            Lawrence Lachman added a comment - Without the visibility of the sub-task estimation in the plan mode, we have to resort to manually going to each parent issue and adding the sub-task estimations up with a calculator and keeping a separate table - outside of JIRA - that tracks how many hours have been assigned to each team member versus their capacity for the sprint. This is ridiculous. It truly makes the plan mode worthless to us because it does not help us do any planning at all.

            +1 for this

            Rebeca Luna added a comment - +1 for this

            Nahue added a comment -

            +1 for this

            Nahue added a comment - +1 for this

            ed.mcculloch, tseano

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

            We see this issue as a valid Suggestion however we cannot provide any guidance at this time as to when, or if, we'll be implementing it.

            For more information on how the JIRA team uses jira.atlassian.com please see https://answers.atlassian.com/questions/110373/how-does-the-jira-team-use-jira-atlassian-com

            Kind regards,
            Martin
            JIRA Agile

            Martin (Inactive) added a comment - ed.mcculloch , tseano The JIRA Agile team is working hard to improve the product and we are aware of the many requests and comments here on jira.atlassian.com We see this issue as a valid Suggestion however we cannot provide any guidance at this time as to when, or if, we'll be implementing it. For more information on how the JIRA team uses jira.atlassian.com please see https://answers.atlassian.com/questions/110373/how-does-the-jira-team-use-jira-atlassian-com Kind regards, Martin JIRA Agile

            EdM added a comment - - edited

            Commenting on tickets is ineffectual for Atlassian. There are dozens (probably orders of magnitude more) of issues that have existed in their products for years and years. If you need immediate help, I would use the support ticket route and schedule a call that way. However, be forewarned that you will initially talk to someone that does not have deep product knowledge.

            Your best bet is to go to the Summit's and physically track down the product owners (if available); but have very low expectations.

            EdM added a comment - - edited Commenting on tickets is ineffectual for Atlassian. There are dozens (probably orders of magnitude more) of issues that have existed in their products for years and years. If you need immediate help, I would use the support ticket route and schedule a call that way. However, be forewarned that you will initially talk to someone that does not have deep product knowledge. Your best bet is to go to the Summit's and physically track down the product owners (if available); but have very low expectations.

            Sean ONeil added a comment -

            How do we get this implemented, this is a huge fundamental hole with this tool. In planning stories should be broken into sub tasks and estimated. Different people will implement different tasks of the story. In planning we need to understand easily and intuitively what each team member has on their plate, it makes the planning session so much more efficient. Other tools do this, it is very basic. I would very much like to have a discussion (phone call) with the product owner here at Atlassian, so I can better understand the logic. I read (http://blogs.atlassian.com/2012/09/agile-qa-greenhopper-time-estimates-with-sub-tasks/) and it does not talk to the issue.

            Please fix this, it is a huge bug.

            Thanks.

            Sean ONeil added a comment - How do we get this implemented, this is a huge fundamental hole with this tool. In planning stories should be broken into sub tasks and estimated. Different people will implement different tasks of the story. In planning we need to understand easily and intuitively what each team member has on their plate, it makes the planning session so much more efficient. Other tools do this, it is very basic. I would very much like to have a discussion (phone call) with the product owner here at Atlassian, so I can better understand the logic. I read ( http://blogs.atlassian.com/2012/09/agile-qa-greenhopper-time-estimates-with-sub-tasks/ ) and it does not talk to the issue. Please fix this, it is a huge bug. Thanks.

            pretty please i meant

            Marla Landolt added a comment - pretty please i meant

            prettylease

            Marla Landolt added a comment - prettylease

            not too optimistic that this will ever happen the issue was created 2012

            Jürgen Kajdocsy added a comment - not too optimistic that this will ever happen the issue was created 2012

            Absolutely. This is a pain point for the entire JIRA Agile fraternity. Unfortunately, this is not on the roadmap of Atlassian yet ( anybody with a revised update may please let us all know).

            Jimmy Francis added a comment - Absolutely. This is a pain point for the entire JIRA Agile fraternity. Unfortunately, this is not on the roadmap of Atlassian yet ( anybody with a revised update may please let us all know).

            Agree this is very important for us too.

            Kevin Miller added a comment - Agree this is very important for us too.

            That's REALLY important to us, as we estimate only the sub-tasks and we really like the option to show estimation including sub-tasks. now we have to do double estimation to see it in the plan mode.

            Ron Grosberg added a comment - That's REALLY important to us, as we estimate only the sub-tasks and we really like the option to show estimation including sub-tasks. now we have to do double estimation to see it in the plan mode.

            Anthony added a comment -

            Same here... this is making it difficult when trying to plan how long a sprint should be, and how much work should go in. It's also affecting our reports when we look at estimated times and compare it to actual logged time.

            Anthony added a comment - Same here... this is making it difficult when trying to plan how long a sprint should be, and how much work should go in. It's also affecting our reports when we look at estimated times and compare it to actual logged time.

            (thumbs up)

            Angie Canon added a comment - (thumbs up)

            Michael added a comment -

            In regards to the original ticket created here - is there any update on this? it is critical that this gets fixed/update as it is causing a lot a reports to be miscalculated and forces me to add things up manually. Please give an update on this ticket.

            Michael added a comment - In regards to the original ticket created here - is there any update on this? it is critical that this gets fixed/update as it is causing a lot a reports to be miscalculated and forces me to add things up manually. Please give an update on this ticket.

            Janos Biro added a comment -

            Hi Angie,

            I don't have permission to open that ticket, but if it is something we could handle within Plangle, let us know

            Cheers,
            Janos

            Janos Biro added a comment - Hi Angie, I don't have permission to open that ticket, but if it is something we could handle within Plangle, let us know Cheers, Janos

            @davidSutton

            Right on! We love you, Atlassian, but, yes, this is so true. Ticket https://support.atlassian.com/servicedesk/customer/portal/23/JST-99570 as evidence. "You're using it the wrong way," in short, even though I'm using it in a way you can use it.

            Angie Canon added a comment - @davidSutton Right on! We love you, Atlassian, but, yes, this is so true. Ticket https://support.atlassian.com/servicedesk/customer/portal/23/JST-99570 as evidence. "You're using it the wrong way," in short, even though I'm using it in a way you can use it.

            Janos Biro added a comment - - edited

            Hi Liz,

            PM Types are actually labels, used to indicate the type of work the given subtask represents, like "Frontend", "Backend", etc.

            After you have configured a custom field in JIRA (it must be "Select list (single choice)" type) and set this field on our Configuration screen as "PM type field", you can set the PM Type of a sub-task using the context menu of that (right click on the sub-task).

            Here you can also find pictures about the feature
            https://moresimp.atlassian.net/wiki/display/APD/Issue+Editor#IssueEditor-EditingissuetypeandPMtype

            Also, PM types are automatically assigned to quick subtasks (basically you can define columns and entering an estimation we create a subtask for you with the predefined suffix, issue type and PM type)
            https://moresimp.atlassian.net/wiki/display/APD/Configuration#Configuration-Quicksub-tasks

            I hope it helped,

            Please let me know if I can help you further on this,

            Cheers,
            Janos

            Janos Biro added a comment - - edited Hi Liz, PM Types are actually labels, used to indicate the type of work the given subtask represents, like "Frontend", "Backend", etc. After you have configured a custom field in JIRA (it must be "Select list (single choice)" type) and set this field on our Configuration screen as "PM type field", you can set the PM Type of a sub-task using the context menu of that (right click on the sub-task). Here you can also find pictures about the feature https://moresimp.atlassian.net/wiki/display/APD/Issue+Editor#IssueEditor-EditingissuetypeandPMtype Also, PM types are automatically assigned to quick subtasks (basically you can define columns and entering an estimation we create a subtask for you with the predefined suffix, issue type and PM type) https://moresimp.atlassian.net/wiki/display/APD/Configuration#Configuration-Quicksub-tasks I hope it helped, Please let me know if I can help you further on this, Cheers, Janos

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

                Created:
                Updated: