| Warning |
|---|
This feature is not yet stable. It is in preparation for the next release and will be available until end of June 2012. |
...
| Tip |
|---|
Even though it might be difficult to understand in the beginning, it is very simple. It's basically all about the component time planning value. By setting a generic plan value on component level, you decide that this value should be used for calculating the results for the project (top-down approach, not very detailed). By not setting it, you decide that the calculated result for the component (= work estimates for all task/sub-tasks of the component) should be used for calculating the project time budget (bottom-up approach, detailed). |
Examples
Have a look at the following example:
...
| Info |
|---|
If you don't use components and/or if you have tasks without component assignment, such tasks will be automatically summed up into a "virtual" component provided by ictime in order not to break the logic that all calculated values always need to come from the next-lower level("No Component"). You can't set a generic plan value for this "component" of course, but the calculated value will be considered for the project like it were a real component. This way, work estimates on task level are made available to calculate the planning value for the project without having a real component. |
Setting Plan Values
Work Estimates (Issue Level)
Plan values on the level of tasks and/or sub-tasks are managed via the respective JIRA functionality. See http://confluence.atlassian.com/display/JIRA/Logging+Work+on+an+Issue#LoggingWorkonanIssue-Specifyingtimeestimates and Work Estimates, Remaining Estimate.
Component
Project
Target/Actual Comparison (Reports)
Accuracy / Planning Progress
...