...
When accessing the plan/actual comparison via the ictime navigation, you have to choose a project first when entering the plan/actual comparison.
Basic Structure of the Plan/Actual Comparison
...
The filter bar helps you to restrict the display to a project (only if called via ictime navigation) and component.
XXX
| Info |
|---|
If you filter by component, the plan/actual comparison value on project level will not consider this filter. Reason is that plan values might be generic, and it does not make sense to compare a generic plan value that has been set for a whole project with real values that are filtered and do not include all components. |
...
This is the highest plan/actual comparison level.
| Field | Description | Remarks | ||
|---|---|---|---|---|
| Plan | Plan value on project level. | either generic or as result of all plan values of all components | ||
| Actual | Work (time) logged on all issues of the project. | Remaining | Sum of all remaining estimates for all issues of the project. | |
| Difference | Plan minus time logged. | due to JIRA options for handling of remaining estimate this value is not necessarily the same like "Remaining"the remaining estimates | ||
| Quality | A quality factor for the overall project planning. The indicator is calculated based on the quality factor of all components. | The quality factor can only be calculated if there is at least one issue that
|
...
This is the second plan/actual comparison level. If you did not define components for your project in JIRA, ictime will automatically display a component "Without Component".
XXX
| Field/Option | Description | Remarks |
|---|---|---|
| Plan | Plan value for component. | Can either be generic or retrieved form the issues of this component, see Planning Sheet and Planning Concept. |
| Logged | Work (time) logged for all issues belonging to this component. | |
| Remaining | The "remaining estimate" value from the respective JIRA field for all issues of that component. | Keep in mind that this is not necessarily the difference between plan and logged, as JIRA offers various options how to set the remaining value when cerating/editing an issue and when logging work. |
| Difference | This is the real effective difference between planned and logged for all issues of that component. | |
| Quality | Quality indicator for planning on the level of this component. The indicator is calculated based on the plan/actual difference of issues of that component that are resolved or closed, and we consider the plan value amount, so issue with high plan values have an higher impact on the quality factor compared to issues that have low time estimates. | The quality factor can only be calculated if you have at least one issue that
|
...