| 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 componenetcomponent, deactivate non-working issue operation option. |
...
This is the highest planning level.You can either enter a "generic" value here or you decide that the total plan value for the project will be taken from the plan value of all components.
Click into the "Update" if you have made changesUse generic" field to inline-edit. If you leave the field, your data is automatically saved. Same applies if you switch between "Use generic" and "Use from components".
| Tip |
|---|
If you have already done a detailed planning on component level, you should always decide to use the sum of all component plan values as total project plan value. If you are in the very beginning of your planning, it might make more sense to set a "generic" value which in fact will be something like an "educated guess" about your project time budget. When you feel that your planning on lower levels is getting better, you will decide to switch. For details, refer to Planning Concept. |
...
This is the second planning level. Similar to the project level, you can either decide to set a "generic" value or to take the plan values from all issues of this component. If you did not define components for your project in JIRA, ictime will automatically display a component "Without Component".
Click into the "Update" if you have made changesUse generic" field to inline-edit. If you leave the field, your data is automatically saved. Same applies if you switch between "Use generic" and "Use from issues".
| Tip |
|---|
If you have already done a detailed planning on issue level, you should always decide to use the sum of all issue plan values as total component plan value. If you are in the very beginning of your planning on issue level, it might make more sense to set a "generic" value which in fact will be something like an "educated guess" about your component time budget. When you feel that your planning on issue level is getting better, you will decide to switch. For details, refer to Planning Concept. |
When clicking on the component, you get access to all issues of the component and can plan on issue level (see next chapterbelow).
...
Plan Time for Issues
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.
Click into the "Estimate" field to inline-edit. If you leave the field, your data is automatically saved.
| Field/Option | Description | Remarks | |||
|---|---|---|---|---|---|
| Task | Task key (clickable, directs you to the issue screen), name, type and status | Assignee | Assignee of this issue|||
| Type | Issue type | ||||
| Status | Issue status | ||||
 | All available operations for Assignee | Assignee of this issue | |||
| Estimate | Enter or modify plan value ("work estimate") for this issue. Simply click into the field to inline-edit. If you leave the field, your data is automatically saved. 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). |
...