Info | ||
---|---|---|
| ||
The following features have been added for version 2.0.1: auto-update and inline-editing, correct handling of issues assigned to more than one componenet, deactivate non-working issue operation option. |
The planning sheet is a central place for setting plan values on the level of project, component and issue. Before using the planning sheet, please make yourself familiar with the planning concept of ictime, specifically with the concept of generic values versus values retreived from lower hierarchy levels (see Planning Concept).
...
When clicking on a component, you get access to all issues of that component and can plan time on these issues. Issues will only be loaded in this moment, and we will store in your session that you have opened this component. This setting will be kept, even if you navigate through JIRA or ictime.
This way, you can plan time (make "work estimates") for all issues in one place.
...
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 | Enter or modify plan value ("work estimate") for this issue. Changes automatically apply the delta to the "remaining estimate" field. | Uses the respective JIRA field. If you have set this value when creating or editing the issue, it will of course be displayed here. If you change it here, it will also change in JIRA interfaces. |
Update | Click when you have made changes | |
Remaining Estimate | The remaining estimate. | Uses the respective JIRA field. If you have set or changed this value when creating or editing the issue or when logging work, the current value of course be displayed here. If you change the plan value here, this will always automatically modify the remaining estimate (with the delta of your plan change). |
If an issue is assigned to more than one component, it will only appear once in the planning sheet. It will be displayed with the component that is the first in alphabetical order.
Info |
---|
Please note that - contrary to normal JIRA behaviour - in this interface, you can also plan time on issues that have already been closed. This is basically intended to allow for "ex-post" planning. |
...