This page displays information relating to the milestone.
General
A milestone represents a significant stage in a project’s life. It consists of a list of issues, ordered by the relative priority that a project manager has assigned them. Milestones make it easier to schedule and track a project through to completion by breaking up the project into smaller, more manageable pieces.
The General tab for the milestone contains basic information about the milestone. Depending on your permissions, you may be able to update this information.
To make changes to a milestone’s details:
-
Make the changes you desire, then click the Apply button.
To abandon changes before you have applied them:
-
Click the Reset button. The fields will be restored to their previous values.
To manage the allocation of users’ time to this project:
-
Click the Manage User Allocation link that can be found on the top left of this tab.
To manage this milestone’s project:
-
Click the Project link that can be found on the top left of this tab.
Description of form fields
| Name | The name of the milestone. This should be something short and descriptive, such as ‘First draft of marketing materials’. It is helpful to prefix the name by something such as ‘M1’ or ‘M2’ (to indicate the milestone’s position in the project), to make it easier to refer unambiguously to a particular milestone when conversing with your colleagues. Thus, the final name of the milestone might be ‘M1 – First draft of marketing materials’. |
|---|---|
| Desired end date | The date by which the project’s manager wishes the milestone to be completed. This is simply used as a point in time against which a project manager can measure a milestone’s expected and planned completion dates. It is shown on Gantt charts by an orange diamond. |
| Users start work on this milestone |
This setting determines how Ketura calculates project schedules. If Together is chosen, then Ketura will calculate schedules based on the assumption that no users will begin work on the milestone until all the work has been completed on the previous milestone. Alternatively, if Separately is chosen, Ketura will calculate schedules assuming that each user with work on this milestone will start as soon as he or she has completed their work on the previous milestone. Which option is appropriate will depend on your intentions: choose Together if you wish all work to be completed on the previous milestone before anyone starts on this one. Otherwise, if you want each user to begin work on the milestone as soon as they are able, even if other users still haven’t finished on the previous milestone, select Separately. |
Issues
This tab shows the milestone’s issues. Each issue represents a small step on the way to completing the milestone.
To change the amount of information shown for the issues:
-
Choose Less detail or More detail from the first Filter by drop-down.
To view more information about an issue:
-
Click the issue’s id in the milestone table. This will link to the appropriate issue page.
To create a new issue on this milestone, or to add existing issues to the milestone by searching, or by entering their ids:
-
Click the Add Issue... button.
To remove one or more issues from the milestone:
-
Select the issues that you wish to remove by checking their checkboxes in the issue table.
-
Click the Remove button.
To perform an action on several issues at once:
-
Select the issues upon which you want to act by checking their checkboxes in the issue table.
-
Click the Act On... button.
To view a summary of several issues in a form suitable for printing:
-
Select the issues for which you wish to print a summary by checking their checkboxes in the issue table.
-
Click the Print... button.
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 still have work outstanding, or those with tasks remaining for a particular user.
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 issue table.
The filter option <tasks remain for...> will match all issues, regardless of whether any work remains on them or not.
About issue priorities
The issues in the milestone are shown in order of their relative priority, highest at the top, as assigned by the project’s manager. The priority of an issue within the milestone is simply a number between 1 (highest priority) and 999 (lowest priority). Issues in the milestone that have the same priority are ordered by their id, from lowest to highest.
Ketura schedules the issues in the order shown (that is, highest priority first). This ordering is reflected in users’ Pending and In progress task lists. Consequently, the project manager’s priorities are immediately apparent to users when they choose which tasks to work upon.
To change the priority of one or more issues:
-
Enter the new priority in the Priority column for each issue that you want to change.
-
Click the Apply button.
If you change your mind before clicking Apply, you can reset the priorities back to their original values by clicking the Reset button.
Description of table columns
| Issue | The unique id of the issue. This is a link to the issue’s management page. |
|---|---|
| Summary | The short summary of the issue, followed, in square brackets, by the issue’s state, severity, type and topic (as a link if you have permission to view the issue topic). |
| Planned Work | An aggregate of the planned work for the tasks of the issue. |
| Work Done | The sum total of the work done on the issue. This value is derived from users’ work journals. |
| Work Remaining | The estimate of the expected work remaining for the issue. |
| Variance |
The difference between the planned work and the expected total work (which is sum of work done + expected work remaining). The variance is shown in red if the amount of work is higher than the project manager expected, or green if it is lower or the same as expected. |
| % Complete (Expected Work) |
The ratio, expressed as a percentage, of the milestone’s work done to the expected total work (which is sum of the milestone’s work done + expected work remaining). This column displays the combined estimates from all milestone task assignees of the progress towards completing the milestone. |
| Priority | Within a particular milestone, each issue has its own priority. This is a number between 1 (highest priority) and 999 (lowest priority), and determines the relative ordering of issues within the milestone. Ketura schedules issues with a higher priority before those with a lower priority. By adjusting issue priorities within each milestone, project managers can ensure that work progresses in the desired order. |
| Selection | A checkbox that, when checked, selects the issue. Selected issues are highlighted with a blue background. You can select all the issues in the current table page by clicking the checkbox in the column’s heading. |
Gantt
This chart shows the expected and planned timing and duration of the issues in the milestone.
Expected schedules are calculated based upon the expected work remaining for all the tasks in the issues, and so indicate the expectations of the people to whom outstanding tasks are assigned. Planned schedules are based on planned work for all the tasks in the issues, taking into account work done. Planned schedules therefore show the intentions of the project’s manager.
Because both expected and planned schedules are shown, it is very easy to see whether each issue is broadly on-track.
Showing only the issues of interest
It is possible to filter the issues displayed on the Gantt chart by a number of factors. This makes it easy, for example, to show only those issues that still have work outstanding, or those with tasks remaining for a particular user.
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 issue table.
Detail
The tables on this tab provide information about the milestone: how long it is likely to take, the quantity of work involved, and the cost of that work.
The quantity of information available about the milestone can be overwhelming, particularly for users new to Ketura, so by default a more restricted set of information is shown.
To change the amount of information shown for the milestone:
-
Choose More detail or Less detail from the Show drop-down list box.
About unassigned tasks
Some tasks in your milestone’s issues might not yet be assigned to particular people. Because Ketura does not know the identity or availability of those who will be working on these tasks, this has two important consequences:
-
Ketura ignores unassigned tasks when calculating schedules. This can make the schedules less accurate than they otherwise might be. Ketura therefore shows a warning triangle against information that is potentially inaccurate due to ignored unassigned tasks.
-
Ketura ignores unassigned tasks when calculating costs.
The different types of information: desired, expected, planned, actual and baseline
The tables on this tab contain several different sorts of information:
-
Desired schedule information relates to the Desired end date specified for the milestones by the project’s manager.
-
Expected information is calculated based upon the expected work remaining for all the tasks in the milestone’s issues, and so represents the expectations of those to whom outstanding tasks are assigned.
-
Planned information is calculated using the planned work for all the tasks in the milestone’s issues, taking into account work done. Planned information therefore indicates the intentions of the project’s manager.
-
Actual information indicates what as actually happened, based on users’ work journals.
-
Baseline information is simply the planned information, as it was at the date set on the tab for baseline comparisons (the date for baseline comparisons is only shown when More detail is selected). Ketura takes snapshots of certain project and milestone information at the end of each day so that it is able to provide baseline comparisons.
Date variances are shown in red if the scheduled date, work effort or cost is worse than the project manager expected, and green if equal to or better than expected.
Other factors affecting the schedule
Other than the amount of work remaining (planned or expected), project schedules are also affected by when users are available to do work, as determined by their availability and allocation calendars. This means that factors such as holidays and sickness, as well as the allocation of users’ time to various projects, is taken into account automatically.
The schedules of individual milestones also depend upon when the work in any preceding milestones is predicted to be completed. Schedule predictions will take into account whether Ketura has been told (on the General tab of the relevant Manage Milestone page) that users will start their work on the milestone together, when all the work on previous milestones has been completed, or separately, as soon as each user has completed his or her work on previous milestones.
To change the baseline comparison date:
-
Click the ... button after the For baseline comparisons, use data from date entry field.
-
Then, in the pop-up calendar that appears, click on the date that you wish to use as a baseline.
-
Or, you can type the date manually and the press the Apply button.
Schedule
The schedule tables provide information about the timing of the milestone.
For a description of the meaning of the different types of information (desired, expected, planned, actual, baseline), see
the main explanation for this tab above. Unassigned tasks are ignored when calculating schedules, again as explained above.
Description of table columns
| Start Date | The dates on which the milestone was planned to start (planned), is expected to start (expected), has started (actual), or was planned to start as of the baseline date (baseline). |
|---|---|
| Completion Date | The dates on which the milestone is expected to end (expected), has ended (actual), project was planned to end (planned), or was planned to end as of the baseline date (baseline). |
| Duration | The duration (in days) of the milestone (from start to end) as is expected (expected), has happened (actual), was planned (planned), or was planned as of the baseline date (baseline). |
| Variance to Planned | The variance (expressed in days and as a percentage) of the actual or expected duration when compared to the planned duration. The variance is shown in red if the duration is longer than the project manager expected, or green if it is shorter or the same as expected. |
| Variance to Baseline (Planned) | The variance (expressed in days and as a percentage) of the actual, expected, or planned, durations when compared to the planned duration as of the baseline date. The variance is shown in red if the duration is longer than the project manager expected, or green if it is shorter or the same as expected. |
Work effort
The work effort table provides information about the amount of work needed for the milestone.
For a description of the meaning of the different types of information (desired, expected, planned, actual, baseline), see
the main explanation for this tab above. Unassigned tasks are ignored when calculating costs, again as explained above.
Description of table columns
| Work Done | The actual amount of work done on the milestone thus far, or the actual amount done on the milestone as of the baseline date. |
|---|---|
| Work Remaining | The amount of work remaining on the milestone as planned (planned), expected (expected), or as was planned as of the baseline date (baseline). |
| Work Total | For the Actual or Expected row, this is simply the sum of Work Done + Work Remaining. For the Planned row, this is the total amount of planned work for all of the milestone’s issues’ tasks. For the Baseline (Planned) row, this is the total amount of planned work for all of the milestone’s issues’ tasks as of the baseline date. |
| % Complete |
The ratio, expressed as a percentage, of the milestone’s work done to the expected total work (which is sum of work done + expected work remaining). This column displays the combined estimates from all milestone task assignees of the progress towards completing the milestone. |
| Variance to Planned | The variance as a duration and as a percentage of the actual or expected Work Total compared to the planned Work Total. The variance is shown in red if the duration is longer than the project manager expected, or green if it is shorter or the same as expected. |
| Variance to Baseline (Planned) | The variance as a duration and as a percentage of the actual or expected, and planned, Work Total when compared to the planned Work Total as of the baseline date. The variance is shown in red if the duration is longer than the project manager expected, or green if it is shorter or the same as expected. |
| Issues Complete | The number of issues in milestone that are complete (that is, in an inactive state), out of the total number of issues. |
Cost
The cost table provides information about the cost of the milestone.
Other than for the baseline cost values (which are stored in the daily snapshot that Ketura makes of certain milestone information), cost information is calculated on the current hourly cost of users. Consequently, any changes in a user’s hourly cost over the duration of a milestone are not taken into account.
For a description of the meaning of the different types of information (desired, expected, planned, actual, baseline), see
the main explanation for this tab above.
Description of table columns
| Work Done | The cost of the actual amount of work done on the milestone thus far, or the cost of the actual amount done on the project as of the baseline date. |
|---|---|
| Work Remaining | The cost of the amount of work remaining as planned (planned), expected (expected), or as was planned as of the baseline date (baseline). |
| Work Total | For the Actual or Expected row, this is simply the sum of the Work Done + Work Remaining costs. For the Planned row, this is the cost of the total amount of planned work for all of the milestone’s issues’ tasks. For the Baseline (Planned) row, this is the cost of the total amount of planned work for all of the milestone’s issues’ tasks as of the baseline date. |
| Variance to Planned | The variance as a duration and as a percentage of the actual or expected Work Total compared to the planned Work Total. The variance is shown in red if the cost is higher than the project manager expected, or green if it is lower or the same as expected. |
| Variance to Baseline (Planned) | The variance as a duration and as a percentage of the actual or expected, and planned, Work Total when compared to the planned Work Total as of the baseline date. The variance is shown in red if the cost is higher than the project manager expected, or green if it is lower or the same as expected. |
Users
This tab shows status information for all the users who have performed work on the milestone or have tasks assigned to them in the milestone’s issues. Information is also shown for any unassigned tasks.
The quantity of information available about the milestone can be overwhelming, particularly for users new to Ketura, so by default a more restricted set of information is shown.
To change the amount of information shown for the milestone:
-
Choose More detail or Less detail from the Show drop-down list box.
Description of table columns
| User | The id of the user for whom related milestone information is shown, followed in square brackets by the user’s last and first names. If you have permission to view the management page for the user, the id is a link to that page. |
|---|---|
| Planned Work | The planned work for all the tasks in the milestone’s issues that are currently assigned to the user. The total planned work is shown, even for any tasks currently assigned to the user that have had work performed on them while previously assigned to another user. Therefore, if you are concerned about the absolute accuracy of this figure, it is recommended that tasks that have work performed on them not be re-assigned: a new task, assigned to the new user, should be created instead of reassigning an existing task. |
| Work Done | The work done thus far by the user for all the tasks in the milestone’s issues, whether or not currently assigned to the user. |
| Expected Work Remaining | The expected work remaining for all the tasks in the milestone’s issues that are currently assigned to the user. |
| Work Total | The sum of the Work Done + Expected Work Remaining columns. |
| Work Variance | The variance of the Work Total to Planned Work (that is, Work Total - Planned Work), expressed as a quantity, and as a percentage relative to Planned Work. The variance is shown in red if the amount of work is higher than the project manager expected, or green if it is lower or the same as expected. |
| Cost Thus Far | The total cost of the work done thus far by the user for all the tasks in the milestone’s issues, whether or not currently assigned to the user. Cost information is calculated on the current hourly cost of users. Consequently, any changes in a user’s hourly cost over time are not taken into account. |
| Expected Total Cost | The total cost of the total amount of work (Work Total) expected to be performed by the user on this milestone. This is the sum of the Cost Thus Far + the cost of the Expected Work Remaining. Cost information is calculated on the current hourly cost of users. Consequently, any changes in a user’s hourly cost over time are not taken into account. |
| % Complete (Expected Work) | The ratio, expressed as a percentage, of the milestone’s Work Done to the Work Total for the user. This figure therefore indicates the user’s perception of their progress thus far on the milestone. |
| Actual or Expected Start Date | The date upon which the user first performed work on this milestone or, if he or she has not yet commenced work, the date on which the user is expected to begin work. This expected figure is based on the schedule calculated using the expected work remaining for all the tasks in the milestone’s issues. |
| Actual or Expected End Date | The date upon which the user completed all his or her work on this milestone or, if the user has not yet commenced work, the date on which he or she is expected to complete work. This expected figure is based upon the schedule calculated using the expected work remaining for all the tasks in the milestone’s issues. |
| Duration | The duration (in days) for the user from the Actual or Expected Start Date to the Actual or Expected End Date. |
Trends
The graphs on this page show the trends over time of the various milestone work effort and cost figures. This essential information makes it possible to see at a glance whether or not a milestone is on-track and heading successfully toward completion.
Because the graphs show trends over the milestone’s lifetime, it is possible to spot potential sources of trouble (such as new work being added to the milestone as fast as existing work is completed) that might not be noticeable from the current information shown on the milestone’s Detail tab.
Work chart
This chart shows how the milestone’s work figures (expressed in days on the Y axis) change over time (the X axis). If work is ongoing on a milestone, the expected work remaining line should trend towards zero over time, if the milestone is ever to complete.
Description of chart series
| Baseline | The planned amount of total work for the milestone (as indicated by the Planned Work Total figure on the Detail tab) as it was on the baseline comparison date. |
|---|---|
| Planned | The total planned work for all the tasks in the milestone’s issues (as indicated by the Planned Work Total figure on the Detail tab), as it has changed over time. |
| Expected Total | The total expected amount of work (the sum of the Done + Expected Remaining trends), as indicated by the Expected Work Total figure on the Detail tab, as it has changed over time. |
| Expected Remaining | The expected work remaining for all the tasks in the milestone’s issues (as indicated by the Expected Work Remaining figure on the Detail tab), as it has changed over time. |
| Done | The work done for all the tasks in the milestone’s issues (as indicated by the Actual or Expected Work Done figure on the Detail tab), as it has changed over time. |
Cost chart
This chart shows how the milestone’s cost changes over time and is particularly useful if you are trying to meet particular cost targets. If work is ongoing on a milestone, the expected total cost line should be fairly constant if the milestone’s costs have been accurately predicted and are under control.
Description of chart series
| Baseline | The cost of the planned amount of total work for the milestone (as indicated by the Planned Work Total figure on the Detail tab) as it was on the baseline comparison date. |
|---|---|
| Planned | The cost of the total planned work for all the tasks in the milestone’s issues (as indicated by the Planned Work Total cost on the Detail tab), as it has changed over time. |
| Expected Total | The cost of the total expected amount of work (the sum of the Done + Expected Remaining trends), as indicated by the Actual or Expected Work Total cost on the Detail tab, as it has changed over time. |
| Expected Remaining | The cost of the expected work remaining for all the tasks in the milestone’s issues (as indicated by the Actual or Expected Work Remaining figure on the Detail tab), as it has changed over time. |
| Expended | The cost of the work done for all the tasks in the milestone’s issues (as indicated by the Actual or Expected Work Done cost on the Detail tab), as it has changed over time. |
How Ketura obtains the information shown by the graphs
At the end of each day, Ketura records certain information about projects and milestones. This snapshot information is used to create the trend graphs. This means that if, for example, the Ketura server is stopped for several days, historical trend information for that period will not be available.
The baseline comparison date
It is possible to choose a baseline comparison date. A horizontal line is drawn on the graphs showing the planned work or cost figure as recorded on the baseline date. This is useful for comparing the trend lines against what was planned on a particular baseline date.
To change the baseline comparison date:
-
Click the ... button after the For baseline comparisons, use data from date entry field.
-
Then, in the pop-up calendar that appears, click on the date that you wish to use as a baseline.
-
Or, you can manually enter the date.
Trends that might indicate a milestone in difficulty
There are several trends that can indicate problems in a milestone.
-
Expected remaining trend is flat or rising. This indicates that as much (or more) work is being added to the milestone as time passes as is being completed. This could be indicative that the scope of the milestone is inadequately understood, and is likely to mean that the milestone will significantly overrun its intended completion date. If so, action should be taken so to better understand the remaining work on the milestone, so that it can be added to the system now and then properly tracked through to completion. It might also be necessary to take steps to reduce the amount of work being added to the milestone, for example, by taking a firmer line with a customer who is continually changing a milestone’s requirements.
-
Expected total trend is rising. This means that work is being added to the milestone over time. For some milestones, this might be normal, but it could indicate that the milestone’s scope is poorly understood.
-
Planned trend is diverging from the expected total trend line. Ketura makes it possible for a project manager to track his or her plan for a milestone (planned values) against what has actually happened and the expectations of those to whom work is assigned (the expected values). If the project manager and those doing work are able accurately to predict the amount of work on the milestone, the planned and expected total trend lines should be quite similar. If they are not, it might be necessary to look at ways of improving the way that project managers and/or task assignees calculate their estimates.
-
Work done trend is not rising steadily. If the work done trend line is rising only slowly, it is possible that the people to whom work is assigned are not able to spend as much time on the milestone’s project as anticipated. The relevant project’s Allocation tab can be used to diagnose such problems.
Activity
This tab shows details of work carried out on the issues of this milestone.
The first section shows the changes that have been submitted to SCM systems within a particular period, for issues of this milestone.
The final two sections show a breakdown of all the work performed on the milestone’s issues’ tasks within a particular period of time, summarized by user and by issue. The information is calculated from all work journal entries with a start time within the chosen period.
To change the period for which activity information is shown:
-
Select one of the time periods (Today, Yesterday, This month, etc) in the For period drop-down. The From and To dates will be adjusted automatically.
-
Or, choose the From and To dates for the period you desire using the associated ... buttons or by manually entering in the dates, then click Apply. The For period drop-down will be adjusted automatically.
However you select the date range, only work entries that start or end within that range will be shown.
Changes
The Changes table shows the sets of changes associated with the issues of this milestone for changes subbmitted to the SCM system in the chosen time period. A single change set might span several pages in the table.
About SCM systems and changes
Ketura is able to integrate with certain version control and software configuration management systems (SCMs) such as Perforce and Subversion. The SCM systems that Ketura monitors are configured on the SCM tab of the System Administration > System Settings page within Ketura. Each configured system is periodically checked to associate changes (i.e. a Perforce changelist or a Subversion repository revision) with individual Ketura issues and milestones.
Ketura will associate a set of changes with an issue if the description in the SCM system contains the issue’s id (e.g. ‘I1234’) as a distinct word. For example, the following three descriptions would all associate a set of changes with the related issues:
I1234: A change set description.
These changes address issues I1234 and I5678.
Fixed problem with the colours (I1234).
A single change set can be associated with multiple issues.
Viewing changes in your web browser
If the SCM repository related to a particular change is available from a web server (e.g. Perforce P4Web or Subversion ViewVC) and this has been appropriately configured in Ketura, it might be possible to view a change or set of changes in your web browser.
To view a change or set of changes in your web browser:
-
Click the View link related to the change or set of changes you wish to view.
Viewing changes with Araxis Merge
If you have Araxis Merge installed on your Mac OS X or Windows computer, you can take advantage of its advanced file comparison capabilities to view the differences between revisions of a file before and after a change. A benefit of using Araxis Merge is that this avoids certain limitations that might apply to the SCM system’s web access to the repository. For example, P4Web does not highlight changes within lines when comparing files; neither can it show the differences between binary files. Araxis Merge, in contrast, offers syntax highlighting of certain file types, highlighting of changes within lines, and is even able to extract and compare the text content of several popular file formats, including Microsoft Word documents.
Ketura integrates with Merge to enable you to view a change or change set simply by clicking on the appropriate Araxis Merge in the Changes table. When you click on the link, your browser will download a small .keturacomparison file to your computer, telling Merge which files to fetch and compare from the SCM system. Merge can automatically read this file and open the appropriate comparison or comparisons. If necessary, Merge will also prompt you for your SCM log on details so that it can fetch the appropriate files from the SCM system. Note that you can safely delete any .keturacomparison files once Merge has opened them (newer versions of Merge might automatically move the files to the Trash or Recycle Bin).
Preparing your computer to use Araxis Merge to view changes from Ketura
-
Ensure that you have a recent version (2008.3563 or later) of Araxis Merge installed and working on computer. A fully functional 30-day evaluation of Araxis Merge can be downloaded from the Araxis website.
-
If you are using Safari under Mac OS X, complete the following steps:
-
Ensure that Safari is saving downloaded files to your Downloads folder. You can check this on the General page of the Safari Preferences dialog.
-
Make sure that the Watch Downloads folder for Ketura comparison files option on the Application Options > General page in the Araxis Merge Preferences dialog is checked.
To view a change or set of changes with Araxis Merge:
-
If you are using the Safari web browser on Mac OS X to access Ketura, start Araxis Merge. You don’t need to do this on Windows, or for other web browsers on Mac OS X.
-
Click the Araxis Merge link related to the change or set of changes that you wish to view.
Please note that an Araxis Merge link for an entire change set will only be available when there are 30 or fewer changes in the change set (links for individual
changes are always present, however). The change set link is disabled if the set contains more than 30 changes. This to prevent
a Microsoft Windows problem where Windows runs out of needed resources when Merge attempts to open a large number of file
comparisons simultaneously.
-
If necessary, confirm to your web browser that you would like to open the file with Araxis Merge.
-
If Merge requests your SCM system account log in details, provide them. You should only need to do this once for each time Merge is run.
-
Once you have finished with a comparison, you may close it. If you anticipate opening further comparisons in Araxis Merge, leave Araxis Merge running so that it does not have to start (or prompt you for your SCM log on information) again.
Breakdown by user
This table contains a list of all users that have worked on the milestone in the selected time period. A user that has not done any work toward the milestone in the time period will not have an entry in the table, regardless of whether any of his or her time has been allocated to work on the milestone’s project.
See the Users tab of the milestone’s project to find out whether each user has worked the correct, allocated, amount of time on the milestone’s
project in a given period of time.
Description of table columns
| User | The id of the user for whom related information is shown, followed in square brackets by the user’s last and first names. If you have permission to view the management page for the user, the id is a link to that page. |
|---|---|
| Work Done | The total amount of work done on the project by the user in the chosen period, based on the user’s work journal entries. Any work journal entries within the period but dated in the future (i.e. with a start time after then end of today) are ignored, as these cannot represent work that has actually been performed thus far. |
| Cost | The cost of the total amount of work done on the project by the user in the chosen period. This is calculated by multiplying the Work Done column by the user’s current hourly cost. Consequently, any changes in a user’s hourly cost within the period are not taken into account. |
Breakdown by issue
This table contains a list of all the issues that have been worked on in the selected time period.
Description of table columns
| Issue | The id and summary of the issue for which related information is shown. If you have permission to view the relevant issue, the id is a link to the issue’s page. |
|---|---|
| Work Done | The total amount of work done on the issue in the chosen period, based on the user’s work journal entries. Any work journal entries within the period but dated in the future (i.e.with a start time after then end of today) are ignored, as these cannot represent work that has actually been performed thus far. |
| Cost | The cost of the total amount of work done on the project. This is calculated by multiplying the Work Done column by the appropriate user’s (or users’) current hourly cost. Consequently, any changes in a user’s hourly cost within the period are not taken into account. |
Alerts
You can use this tab to have Ketura tell you (via the Alerts tab on your Home Page) when something of interest happens to this milestone.
To indicate which alerts you would like to receive:
-
Check or uncheck the checkboxes next to the alerts in which you are interested.
-
Optionally, change the settings of any alerts which are configurable.
-
Click the Apply button.
To abandon any changes before you have applied them:
-
Click the Reset button.