...
| Info |
|---|
Please note that planning in ictime is always time-based. Even though you can assign a cost/price to you work for time you log, we do not offer financial budget planning at this stage, but just time-planning. Planning is also not related to resource-allocation, so you are not planning who is going to do what, but just which time budgets you expect on the level of project, component and issues. These plan values will then be compared with the time logged in the Plan/Actual interface (see Plan/Actual Comparison). |
| Table of Contents |
|---|
...
Accessing the Planning Sheet
...
| 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" 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".
| 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 chapter).
...
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.
| 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. |
...
Issue Planning on Issue Screen (Work Estimates)Work Estimates
...
)
Plan values on the level of tasks and/or sub-tasks are managed can also be set via the respective JIRA functionality. See http://confluence.atlassian.com/display/JIRA/Logging+Work+on+an+Issue#LoggingWorkonanIssue-Specifyingtimeestimates and Work Estimates, Remaining Estimate.
Please note that - contrary to normal JIRA behaviour - you can also plan time on issues that are already closed.
The main difference - apart from the fact that you have to navigate to the issue - is that work estimates set via JIRA default functionality usually have the option to not automatically modifying the remaining estimate with the delta of your plan change, but the remaing estimate is either left unchanged by default, or you have the choice to leave it unchanged, to set it manually etc.