Home > Ketura > Full Documentation > Manage User Page

Manage User Page

This page lets you manage a user.

Contact details

A Ketura user is someone who is being managed using the Ketura system and for whom an account on the Ketura server has been created. Each user is a member of a group, which in turn determines the permissions that a user possesses. Only active users are allowed to log on to the system. For background information on users, see Ketura Tour Step 6: Users and Contacts.

Depending on your permissions, you may be able to perform the actions below.

To update the user’s details:
To abandon changes before you have applied them:

Description of form fields

First name The first name of the user.
Last name The last name of the user.
Email The email address of the user. If entered, basic validation of the email address is carried out.
Job title The job title, if relevant, of the user.
Company The name of the company with which the user is associated, if relevant.
Address The first line of the postal address of the user.
Address The second line of the postal address (should one exist) of the user.
City The town or city of the user’s postal address.
State/region The state or region of the user’s postal address.
Post/zip code The post/zip code of the user’s postal address.
Country The country of the user’s postal address.
Phone The telephone number of the user. This is a free text field, and as such characters as well as numbers are allowed.
Fax The fax number of the user. This is a free text field, and as such characters as well as numbers are allowed.

Cost

Depending on your permissions, this tab can be used to update the user’s hourly cost.

Although it is not necessary to specify an hourly cost for each user, doing so allows Ketura to calculate and display useful cost related information for projects, milestones, issues and tasks. This allows questions such as ‘How much would it cost to address this issue?’ and ‘How much did the completion of this project cost us?’ to be easily answered.

To update the user’s hourly cost:

The cost information provided by Ketura is calculated on the current hourly cost of users. Consequently, any changes to a user’s hourly cost over the duration of an issue, milestone or project are not taken into account.

To abandon a change before you have applied it:

Sensitivity of cost information

It might be inappropriate to share cost information freely within some organizations. Therefore, Ketura makes it possible (by means of group permissions) to restrict the availability of cost information to only those users who need to have access to it.

Determining the hourly cost of a user

Your organization should have a clear policy to determine how it sets the hourly cost for users. There are several possibilities:

General rounding of calculated costs

Costs calculated using users’ hourly costs are displayed rounded to either 0 or 2 decimal places, depending on the Currency decimal places value on the Regional tab of the System Settings page. When rounding to 0 decimal places, it is possible that minor (and unavoidable) discrepancies in cost totals might be noticed between tables.

Rounding of the stored hourly cost

Ketura always stores users’ hourly costs to a precision of 2 decimal places. Costs entered with a higher precision will be rounded before being stored.

When the system is configured to show costs to 2 decimal places, the Hourly cost field on this tab always shows both decimal places, even when the cost is an integer (non-fractional) value. However, when the system is configured to show costs to 0 decimal places (see above), Ketura will display only as many decimal places (0, 1 or 2) as are required to show faithfully the hourly cost as it has been stored.

Description of form field

Hourly cost The user’s hourly cost, used by Ketura to calculate the cost of the work that the user undertakes.

Notes

This tab lets you store arbitrary notes about the contact.

Depending on your permissions, you may be able to perform the actions below.

To update the contact’s notes:
To abandon changes before you have applied them:

Description of form fields

Notes This field is for arbitrary notes about the contact.

Access details

The user’s access details determine if he or she is allowed to log onto Ketura, and how he or she authenticates him or herself. It also determines what he or she can see and do once logged on.

Depending on your permissions, this tab lets you update the user’s access details.

To update the user’s access details:
To change the user’s password:
To abandon changes before you have applied them:

Description of form fields

User id The name used to identify the user. User ids must be unique, without regard to case. The user id is used in conjunction with a password for a user to access the system. You should be careful to choose a name that does not compromise the level of security you wish to enforce. This name appears at the start of drop-down list boxes that display the users of Ketura.
Group The group to which the user belongs. The group defines the permissions that the user will be granted, and thus determines what the user can see and do.
Active When checked, the user is treated as active for licensing purposes and is allowed to log onto Ketura.

Preferences

Depending on your permissions, this tab lets you update the user’s preferences with regards to the number of rows displayed on a table.

To update the user’s preferences:
To abandon changes before you have applied them:

Description of form field

Rows per table page This is the size, in rows, of tables displayed by Ketura. Be careful not to choose too great a number as large table displays may impact system performance. An odd, rather than even, number of rows generally gives the more pleasing visual effect.

In progress tasks

This tab shows the tasks on which the user is currently working, grouped by issue.

Depending on your permissions, you may be able to perform the actions below.

How tasks reach the user’s in progress list

The user is in control of which tasks from his or her pending list are moved into his or her in progress list. This enables a user to focus on a few tasks at a time. This means that a user does not need to search through a possibly unmanageable number of tasks.

Order of tasks

The tasks in this list are shown in the order that the project manager expects the user to undertake work, taking into account factors such as the order of milestones within a project and relative issue priority within each milestone. Therefore, the user should generally endeavour to complete tasks higher up in the list before commencing those further down.

Why a task might disappear from this list

A task will be removed automatically from the user’s In progress tab if any of the following occur:

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 for a particular topic, only active issues, or those of a particular milestone.

To limit the display of issues to only those of interest:

Changing planned work values of tasks

Depending on your permissions, it is possible to change planned work values.

To change the planned work values of tasks:

Changing work remaining values of tasks

Depending on your permissions, it is possible to change work remaining values.

To change the work remaining values of tasks:

Marking tasks as complete

Depending on your permissions, it is possible to mark selected tasks as complete.

To mark tasks as complete:

Acting on several tasks at once

Depending on your permissions, it is possible to perform several actions (such as reassignment) on any tasks you have selected.

To perform an action on several tasks:
To abandon changes before you have applied them:
To view the personal profile page for this user:
To manage the user’s allocation to this project:

Printing issues from the user’s in progress list

You can print selected issue from the user’s in progress list.

To print issues:

Description of table columns

Issue/Task The id of the issue or task. If you have permission to view the task or issue, this is a link to the item.
Summary The summary of the task or issue. Issue summaries are followed by square brackets containing the issue’s priority, state, topic (as a link if you have permission to view the issue topic) and (if Ketura has been able to determine one) a scheduled date for work to continue on the issue.
Planned Work The planned work for the task. This is the project manager’s estimate of the total amount of work needed to complete the task.
Work Done The total amount of work done on this task to date. If the task has previously been assigned to someone else, this figure might also include work done by them.
Work Remaining Your best, current, estimate of the expected work remaining. This indicates how much more work you expect to be required to complete the task.
Work Variance The variance of the Work Total to Planned Work (that is, Work Total - Planned Work), expressed as a quantity. Where Work Total = Work Done + 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.
Selection A checkbox that, when checked, selects the task. Selected tasks are highlighted with a blue background. You can select all the tasks in the current table page by clicking the checkbox in the column’s heading, or all the tasks in the table that belong to an issue by clicking the checkbox for that issue.

For help working with tables, see Tutorial 1: The Basics of Working with Ketura.

Pending tasks

This tab shows the tasks that are pending for the user, grouped by issue.

Depending on your permissions, you may be able to perform the actions below, as well as change the formatting of time using the Time tab of the System Settings page.

How tasks reach the user’s pending list

A task will appear in the user’s Pending list if all of the following are true:

Order of tasks

The tasks in this list are shown in the order that the project manager expects the user to undertake work, taking into account factors such as the order of milestones within a project and relative issue priority within each milestone. Therefore, the user should generally endeavour to complete tasks higher up in the list before commencing those further down.

Why a task might disappear from this list

A task will be removed automatically from the user’s Pending tab if any of the following occur:

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 for a particular topic, only active issues, or those of a particular milestone.

To limit the display of issues to only those of interest:

Changing planned work values of tasks

Depending on your permissions, it is possible to change planned work values.

To change the planned work values of tasks:

Changing work remaining values of tasks

Depending on your permissions, it is possible to change work remaining values.

To change the work remaining values of tasks:

Marking tasks as complete

Depending on your permissions, it is possible to mark selected tasks as complete.

To mark tasks as complete:

Acting on several tasks at once

Depending on your permissions, it is possible to perform several actions (such as reassignment) on any tasks you have selected.

To perform an action on several tasks:
To abandon changes before you have applied them:
To view the personal profile page for this user:

Printing issues from the user’s pending list

To print selected issues from the user’s pending list:

Description of table columns

Issue/Task The id of the issue or task. If you have permission to view the task or issue, this is a link to the item.
Summary The summary of the task or issue. Issue summaries are followed by square brackets containing the issue’s priority, state, topic and (if Ketura has been able to determine one) a scheduled date for work to continue on the issue.
Planned Work The planned work for the task. This is the project manager’s estimate of the total amount of work needed to complete the task.
Work Done The total amount of work done on this task to date. If the task has previously been assigned to someone else, this figure might also include work done by them.
Work Remaining Your best, current, estimate of the expected work remaining. This indicates how much more work you expect to be required to complete the task.
Work Variance The variance of the Work Total to Planned Work (that is, Work Total - Planned Work), expressed as a quantity. Where Work Total = Work Done + 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.
Selection A checkbox that, when checked, selects the task. Selected tasks are highlighted with a blue background. You can select all the tasks in the current table page by clicking the checkbox in the column’s heading, or all the tasks in the table that belong to an issue by clicking the checkbox for that issue.

For help working with tables, see Tutorial 1: The Basics of Working with Ketura.

Planned tasks

This tab shows the tasks that are planned for the user, but which are not yet pending or in progress, grouped by issue.

Depending on your permissions, you may be able to perform the actions below.

How tasks reach the user’s planned list

A task will appear in the user’s Planned list if all of the following are true:

Order of tasks

The tasks in this list are shown in the order that the project manager expects the user to undertake work, taking into account factors such as the order of milestones within a project and relative issue priority within each milestone. Therefore, the user should generally endeavour to complete tasks higher up in the list before commencing those further down.

Why a task might disappear from this list

A task will be removed automatically from the user’s Planned tab if any of the following occur:

To limit the display of issues to only those of interest:

Changing planned work values of tasks

Depending on your permissions, it is possible to change planned work values.

To change the planned work values of tasks:

Changing work remaining values of tasks

Depending on your permissions, it is possible to change work remaining values.

To change the work remaining values of tasks:

Marking tasks as complete

Depending on your permissions, it is possible to mark selected tasks as complete.

To mark tasks as complete:

Acting on several tasks at once

Depending on your permissions, it is possible to perform several actions (such as reassignment) on any tasks you have selected.

To perform an action on several tasks:
To abandon changes before you have applied them:
To view the personal profile page for this user:

Printing issues from the user’s planned list

You can print selected issue from the user’s planned list.

To print issues:

Description of table columns

Issue/Task The id of the issue or task. If you have permission to view the task or issue, this is a link to the item.
Summary The summary of the task or issue. Issue summaries are followed by square brackets containing the issue’s priority, state, topic (as a link if you have permission to view the issue topic) and (if Ketura has been able to determine one) a scheduled date for work to continue on the issue.
Planned Work The planned work for the task. This is the project manager’s estimate of the total amount of work needed to complete the task.
Work Done The total amount of work done on this task to date. If the task has previously been assigned to someone else, this figure might also include work done by them.
Work Remaining Your best, current, estimate of the expected work remaining. This indicates how much more work you expect to be required to complete the task.
Work Variance The variance of the Work Total to Planned Work (that is, Work Total - Planned Work), expressed as a quantity. Where Work Total = Work Done + 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.
Selection A checkbox that, when checked, selects the task. Selected tasks are highlighted with a blue background. You can select all the tasks in the current table page by clicking the checkbox in the column’s heading, or all the tasks in the table that belong to an issue by clicking the checkbox for that issue.

For help working with tables, see Tutorial 1: The Basics of Working with Ketura.

Work journal

Your work journal is a record of all the work that you have undertaken on tasks. Each entry in the journal records the task that you have worked on, when you worked on it and how much work you did. Ketura uses this information to help managers keep projects and milestones on track and within budget.

Entries are created automatically when you use task work timers, or you can create entries manually.

Depending on your permissions, you may be able to perform the actions below, as well as change the time format using the Time tab of the System Settings page.

To create a new work journal entry:
To delete one or more work journal entries:
To mark one or more tasks as complete:
To abandon changes before you have applied them:
To complete a work journal entry created by starting a task work timer:
To modify existing work journal entries:
To correct a work journal entry created by inadvertently starting a work timer for the wrong task:
To restrict the display of work journal entries to those starting or ending within a particular period:
To change the sort order of the work journal:

How Ketura interprets end times

Ketura tries to interpret any end times you enter the following way:

Overlapping entries

If one work journal entry starts before another ends, Ketura will show a yellow warning triangle against any entry that overlaps with an entry higher up in the displayed table page. Adjust the entries so that they do not overlap to remove the warning.

For efficiency reasons, Ketura only warns you about overlaps in the work journal entries that are currently displayed.

Note also that Ketura stores work journal entry start and end times to the nearest second, even though they are only displayed to the minute. If two entries are shown as overlapping, and the end time of the first is the same (to the nearest minute) as the start time of the second, it is likely that the first entry ends a few seconds after the second starts. In this case, remove the overlap warning by adding a minute to the start time of the second entry, so that the entries no longer overlap.

Locked work journal entries

It is possible for a manager to lock your work journal entries that are on or before a particular date. This is useful if your organization has a particular process for checking and approving work journal entries. A padlock symbol will be shown next to any locked entries and you will be unable to modify them.

Quickly adding tasks to an issue

Ketura makes it quick and easy to add an extra task to any issue in your Pending, In Progress and Work journal tabs (provided, of course, that you have permission to do so). You can even add a task and start logging time to it in a single operation. This makes it very easy to be specific about where your time is going; if you have a major activity, you can give it its own task.

New Task links are provided next to each task and issue in the Pending and In Progress lists, and next to each task in your Work journal. When you click the link, you will be taken to a page where you can specify the new task’s details. If you followed a New Task link next to a task, the fields will be pre-filled with the information from that task. A colon (‘:’) is automatically appended to the task summary, so that you can create what are, in effect, sub-tasks of existing tasks. Simply add an additional description of the sub-task after the colon in the task’s summary. Once you are happy with the task’s other details, you can Apply your changes and be returned directly to your Home Page.

To add a new task to an issue based on an existing task:

Description of table columns

Task The id of the task for which this work journal entry is recording time worked.
Task Summary The summary of the task, prefixed with the task id and followed in square brackets with the task’s issue’s id and summary. If you have permission to view tasks and/or issues, the task and issue ids will be links to the appropriate task or issue.
Start Date The date on which the work recorded by the work journal entry starts.
Start Time The time on which the work recorded by the work journal entry starts. Times are displayed to the nearest minute, although Ketura records them in its database to the nearest second.
End Time The time on which the work recorded by the work journal entry ends. This is typically on the same date as the start date, but might be on the following day if the entry’s duration means that the entry spans midnight. Times are displayed to the nearest minute, although Ketura records them in its database to the nearest second.
Duration The duration of the work recorded by the work journal entry. This is the difference between the start and end times.
Selection A checkbox that, when checked, selects the work journal entry. Selected entries are highlighted with a blue background. You can select all the entries in the current table page by clicking the checkbox in the column’s heading.

For help working with tables, see Tutorial 1: The Basics of Working with Ketura.

Activity by issue

This tab shows how much work the user has done on issues during the specified time period. Depending on your permissions, you may also be able to see the associated cost of the work done.

This table is ordered by issue topic and then by the id of the issue.

To restrict the display of work done on issues to a particular period:

Description of table columns

Issue The id of the issue. If you have permission to view the issue, this is a link to the issue’s page.
Summary The summary of the issue.
Work Done The sum of the work done on the issue by the user in the chosen period, based on the user’s work journal entries.
Cost If permissions allow, the cost of the amount of user’s time indicated in the Work Done column. This is calculated by multiplying the work done by the user’s hourly cost. 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.
Issue Topic The name of the issue topic associated with the issue. If you have permission to view issue topics, this is a link to the topic's page.

For help working with tables, see Tutorial 1: The Basics of Working with Ketura.

Activity by issue topic

This tab shows how much work the user has done on issue topics during the specified time period. Depending on your permissions, you may also be able to see the associated cost of the work done.

To restrict the display of work done on issue topics to a particular period:

Description of table columns

Issue Topic The name of the issue topic. If you have permission to view issue topics, this is a link to the topic's page.
Work Done The sum of the work done on the issue topic by the user in the chosen period, based on the user’s work journal entries.
Cost If permissions allow, the cost of the amount of user’s time indicated in the Work Done column. This is calculated by multiplying the work done by the user’s hourly cost. 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.

For help working with tables, see Tutorial 1: The Basics of Working with Ketura.

Activity by project

This tab shows how much work the user has done on projects. It also shows how much time was allocated (by the project manager) to the user for particular projects. Depending on your permissions, you may also be able to see the associated cost of the work done.

This information is useful as it shows how much work the user has done out of what was expected, indicating clearly how much more work he or she has to do on each project in a particular period to meet project manager’s expectations.

Projects that are alternatives are not shown in the table. For more information on alternative projects, please see the help for the Manage Projects Page. Any work in the specified time period for issues that are not part of a milestone will not contribute to values in the table.

To restrict the display of work done on projects to a particular period:

Description of table columns

Project The name of the project. If you have permission to view projects, this is a link to the project’s page.
Allocated Work The amount of the user’s time allocated to the project in the chosen period. Time is allocated to users on the Allocation calendars tab of the Manage Users page, reached using the global Users tab.
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 (that is, with a start time after the end of today) are ignored, as these cannot represent work that has actually been performed thus far.
Variance The variance of the Work Done to Allocated Work (that is, Work Done - Allocated Work), expressed as a quantity, and as a percentage relative to the Allocated Work. The variance will be highlighted in red if the % Allocated Work Done column is less than 85% or more than 115%. Otherwise, it is highlighted green.
% Allocated Work Done The amount of Work Done, divided by the Allocated Work. It is possible for this figure to be over 100% if the user has done more work than allocated.
Cost If permissions allow, the cost of the amount of the user’s time indicated in the Work Done column. This is calculated by multiplying the work done by the user’s hourly cost. 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.

For help working with tables, see Tutorial 1: The Basics of Working with Ketura.