Reporter |
![]() |
---|---|
Created | Mar 5, 2013 6:43:53 PM |
Updated | Mar 5, 2013 7:24:36 PM |
Priority | Normal |
Type | Feature |
State | Open |
Assignee | Vadim Gurov (vgurov) |
Subsystem | Agile Board |
Fix versions | No Fix versions |
Fixed in builds | No Fixed in build |
Affected versions | No Affected versions |
Browser | Any Browser |
OS | Any OS |
Verified in build | Not verified |
Verified by | Nobody |
Reviewed by | No reviewed by |
Severity | Routine |
So, this is for estimates and story points on the agile boards. We plan to create two custom fields "story points" and "estimate" one being an type enumeration and the other of type period. Can we aggregate these two numbers on parent tickets? For example, lets say, I have an issue of Type "Story" (or Feature) and under that I have two sub stories and each of those two stories have two sub Tasks. Lets say those tasks are estimated at 2 hours each. So, I would like to see the estimate rolled up in each of those two stories as 4 hours each and then i would like to see those numbers rolled up into the top level story as 8 hours. Further, I have story points on those stories. Lets say each sub story was 13 points, then I want to see 26 as the story points number on the parent story. Note that the story point is an enumeration, so, 26 might not be a value in the enumeration, but is an addition of the enumerated values at the lowest level.
Finally, I dont want to be able to edit hour estimates on stories as stories cannot be estimated. Similarly, I dont want to be able to edit story points on tasks as task do not have story points.
We have not run into a very important need for this as yet, because we plan to use this for a small team for now. However, if we ever decide to go forward and implement for the larger company, then this will quickly become an issue/question.
thank you!
Finally, I dont want to be able to edit hour estimates on stories as stories cannot be estimated. Similarly, I dont want to be able to edit story points on tasks as task do not have story points.
We have not run into a very important need for this as yet, because we plan to use this for a small team for now. However, if we ever decide to go forward and implement for the larger company, then this will quickly become an issue/question.
thank you!