Documentation for ictime version 2.x. This documentation relates to an old, non-supported version of ictime. The documentation of the current version can be found here.

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

« Previous Version 10 Next »

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).

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.

 

Accessing the Planning Sheet

You can either access the planning sheet via the JIRA project tab or via the ictime navigation.

Planning Sheet via ictime Navigation

When accessing via the ictime navigation, you have to choose a project first when entering the planning sheet.

Choose a project and click on the "Show" button.

Planning Sheet via JIRA Project Tab

Choose a project via the JIRA project tab and select the navigation tab "Planning":

If you once have entered the planning sheet this way, you can change the project in JIRA and will directly go to the planning sheet for the respective project.

 

Basic Structure of the Planning Sheet

The planning sheet consists of the filter bar, the project section and components.

Filter

The filter bar helps you to restrict the planning sheet to a project (only if called via ictime navigation), component or version (coming soon).

The filter by component, version and user can be combined. It is basically useful if you want to plan on issue level and is intended to restrict the number of issues on your page and to allow you to focus for a specific component, version and/or user.

Project Section

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 "Update" if you have made changes.

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.

Components

This is the second planning level. Similar to the project level

Plan for Issues

 

 

Issue Planning on Issue Screen (Work Estimates)

Work Estimates (Issue Level)

Plan values on the level of tasks and/or sub-tasks are managed 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.

 

 

  • No labels