...
| Field | Description | Remarks |
|---|---|---|
| Plan | Plan value on project level. | either generic or as result of all plan values of all components |
| Actual (Logged) | 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" |
| Quality | A quality factor for the overall project planning. The indicator is calculated based on the quality factor of all components. | TBD |
Plan/Actual Comparison for Components
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 | 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 ot that component that are resolved or closed, and we consider the standard deviation of plan/actual values for all issues of all components. In addition, 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 is calculated as follows: TBD The quality factor can only be calculated if you have at least one issue that
|
...
When clicking on a component, you get access to all issues of that component and can plan time on these issues. This way, you can plan time (make "work estimates") for all issues in one place.
XXX
| Field/Option | Description | Remarks |
|---|---|---|
| Task | Task key (clickable, directs you to the issue screen), name, type and status | |
| Assignee | Assignee of this issue | |
| All available operations for this issue | ||
| Estimate | Plan value ("work estimate") for this issue. | |
| Remaining Estimate | The remaining estimate. | Uses the respective JIRA field. |
| Difference | This is the real effective difference between planned and logged. | |
| Quality | Quality indicator for planning on the level of this component. On issue level, quality is simply time logged divided by time planned. Quality 1 means that plan and actual result are the same, so the planning was perfect. Quality factors > 1 mean that you have spent more time than planned, and < 1 that you have spent less time than planned. | The quality factor can only be calculated if the issue
|