This page lets you re-balance two or more milestones.
Moving issues between milestones is helpful where it is important to meet a particular milestone, but where some of the work currently planned for that milestone can be postponed to a later milestone. Of course, this does not bring forward the completion date of the project as a whole, but that may be of secondary importance.
This tabs lets you compare two or more of a project’s milestones, showing all the issues in each milestone. Each issue can then be moved between milestones with a single mouse click. The effects on the milestone schedules can then be previewed, before the changes are committed.
To move issues between milestones:
- Click the radio button in the column of the milestone to which an issue should be moved.
- Click the Preview button to see a preview of the changes before committing.
- Or, click the Apply button to commit the moves directly.
Showing only the issues of interest
It is possible to filter the list of issues by a number of factors. This makes it easy, for example, to show only those issues that have a particular severity.
To limit the display of issues to only those of interest:
- Choose the criteria by which you wish to filter from the Filter by drop-downs above the table.
To abandon the movement of issues between milestones:
- Click the Cancel button.
To abandon changes before you have applied them:
- Click the Reset button. The fields will be restored to their previous values.
Description of table columns
|Issue||The id and summary of the issue, followed by square brackets containing the issue’s type, severity, state and topic (as a link if you have permission to view the topic). If you have permission to view the relevant issue, the id is a link to the issue’s page.|
|Planned Work||The planned work for the issue. This is the project manager’s estimate of the total amount of work needed to complete the tasks in the issue.|
|Work Remaining||The expected work remaining for all the tasks in the issue.|
|Milestone||Two or more milestone columns may exist, containing radio buttons showing the current position of issues and allowing the movement of issues between milestones.|
Description of table footer
|Actual or Expected End Date||The actual date on which work on the milestone’s issues’ tasks completed or, if work has not yet ended, the expected end date based upon the expected work remaining for all the tasks in the project’s milestones’ issues. The expected date represents the expectations of those to whom outstanding tasks are assigned.|
|Desired End Date||The Desired end date specified for the milestone, as specified by the project’s manager on the General tab of the milestone. This provides a fixed reference point in time against which progress can be measured. Desired end dates are shown on Gantt charts by an orange diamond. The desired end date for the project as a whole is the desired end date for the last milestone in that project.|
|Variance||The difference (in days) between the Actual or Expected End Date and the Desired End Date. The percentage value is the percentage difference between the expected and desired duration (from start to end) of the milestone.|
For help working with tables, see Tutorial 1: The Basics of Working with Ketura.