Glossary of Ketura Terms and Concepts




See System Administrator.


Files such as documents and images can be attached to an issue. The contents of such files are copied into the Ketura database, so once attached, the file used to create an issue attachment can safely be deleted. See Add Attachment Page.

Audit trail

The audit trail contains a list of all the events that have occurred in the system, so it is always possible to find out what happened, and when.



You interact with Ketura by means of a web browser. See a list of supported browsers.



Ketura’s user interface uses web pages comprising forms, tables and charts. Charts allow you to view the information that is held in Ketura in a graphical format.


See Issue Comment.


A contact is a person whose details are known to Ketura. Contacts may be added to an issue (such a contact might be the customer whose bug report has led to the issue being raised).

All Ketura users automatically have contacts generated for them. Learn more.


A cookie is a small piece of information stored by your web browser. Cookies must be enabled in your web browser for Ketura to work properly.

Ketura saves the following information using persistent cookies:

  • The selected tab on Ketura pages that have multiple tabs.
  • Optionally, according to a selection on the log on page, your user id and password, to allow you to start using Ketura from your computer without logging on.

Non-persistent (session) cookies are used to maintain your Ketura session. This information is not stored permanently on your computer, but held for the duration of a session by your browser.


CSV (comma-separated value) is a file format commonly understood by database and spreadsheet programs such as Microsoft Excel and Calc.

A CSV file consists of lines of text separated into fields by commas and optionally enclosed by double-quotation marks (") if commas are allowed to appear within the fields. For example, Research,Archery,Hockey,"Hubble,Deep" represents a line containing four fields.

When you use Ketura to save the contents of tables in CSV format, each table column appears as a CSV field. The sort order of the displayed table, and any date filtering you may have applied (but generally not other types of filter), is honoured in the CSV output. The first line of the CSV file contains the column names.

The CSV files created by Ketura are plain text files using the UTF-8 character encoding.



The information Ketura stores is held in a database managed by a database management system (which may be located on a different server computer from that upon which Ketura itself is installed). The database management system ensures that the data is consistent and offers additional facilities such as backup and restore. Learn more.


See Issue Description.

Durations and work quantities

Durations (periods of time) and work quantities in Ketura are represented by a number followed by a unit abbreviation. For example, you would enter 2.5 h in a work journal entry to indicate a duration of two-and-a-half-hours. The default unit abbreviations are:

m for minutes
h for hours
d for days
w for weeks
mo for months

These abbreviations can be changed on the System SettingsAdministration areasManage System SettingsRegional tab and might therefore be different on your system.



Events are generated whenever the Ketura database is updated. Learn more.

Expected total work

Expected total work is the estimate of the total quantity of work that is required to complete a task, based on the estimate of expected work remaining made by the person to whom a task is assigned and the work done on the task. For issues, milestones and projects, the expected total work is an aggregate of the figures for the relevant tasks.

To learn more about work estimates, see Ketura Tour Step 3: Tasks.

Expected work remaining

Expected work remaining is the estimate of how much work there is left for a task, made by the person to whom a task is assigned. For issues, milestones and projects, the expected work remaining is an aggregate of the estimates for the relevant tasks.

To learn more about work estimates, see Ketura Tour Step 3: Tasks.



Ketura’s user interface uses web pages comprising forms, tables and charts. Forms allow you to update information held in Ketura.



A group is a collection of users. Groups are granted permissions, and it is a user’s membership of a particular group that determines how he or she may use Ketura.



For help with using Ketura, see Start Here.



In Ketura, issues are used to record small-scale goals. More formally, an issue represents a perception by someone (such as a customer, employee, or end-user) of the need for change to occur.

Typical types of issues include help desk support requests, product bug reports or enhancement requests, and documentation errors.

For more information about issues, see Ketura Tour Step 2: Issues.

Issue comment

Any number of Comments can be added to an issue. Such comments can either be in plain text or in a subset of HTML (including, for example, <em> and <strong> tags). The set of comments added to an issue forms its comment history. See Add Comment To Issue Page.

Issue description

Each issue has a description, in which various further information about the issue can be recorded.

Issue id

Each issue has a unique number that identifies it. Issue ids are never reused, even if an issue is completely deleted from the system.

Issue severity

Each Ketura issue has a severity. The severity of an issue indicates the importance of the issue from the perspective of the person experiencing the problem or making the request. The names of severity types are typically configured by the System Administrator. Typical severity types might include “Minor” and “Important”.

Issue state

Each Ketura issue has a state, which defines how far the issue has progressed in the workflow defined to process it.

The available states are typically set by the person who administers your Ketura system, although the system comes with several types already defined as a starting point.

Each state is either active (issues in the state are still outstanding) or inactive (issue in the state have been dealt with and no longer need to be considered).

Typical states might include ‘New’, ‘Resolved’, ‘Rejected’, ‘In Progress’, etc.

Issue Topic

Ketura topics are used to identify what issues are about and therefore serve as a way to categorize issues. What happens to an issue from the time it is created is determined by the workflow configured for its topic. To learn more, see Ketura Tour Step 2: Issues and Ketura Tour Step 8: Workflow.



See Script.


Licence file

To continue using Ketura past the free evaluation period, the product must be licensed. This is accomplished by means of a licence file that you obtain from Araxis. The licence file determines things such as which server machine is licensed to run the Ketura server and the maximum number of users allowed in the system.

Logging on

Before you can access Ketura, you must log on using a user id and password supplied by the System Administrator. From this point, until you log off or your session times out, you maintain a Ketura session. See Log On Page.

Logging off

Log off from Ketura by clicking the Log Off link on the Home Page.



In Ketura, milestones represent significant stages in a project’s life.

For more information about issues, see Ketura Tour Step 4: Projects and Milestones.


Navigation trail

A set of links known as the navigation trail appear at the top left of each page in the system, or at the top right of documentation pages (including this one). The links show you the quickest way to reach the page you are on (not necessarily the route by which you reached it). Each entry in the navigation trail apart from the last is a link that you can follow using your browser.



Permissions control how Ketura is presented to a user and what a user of the Ketura system can do. Each permission controls an individual aspect of Ketura. A user must belong to a group to which the permission has been granted to be able to use the aspect of the system restricted by the permission.

Planned work

Planned work is the project manager’s estimate of how much work should be needed to complete a task, typically based on an initial expected work remaining estimate made by the task’s assignee. For issues, milestones and projects, the planned work is an aggregate of the planned work for the relevant tasks.

To learn more about work estimates, see Ketura Tour Step 3: Tasks.


Ketura relies on your browser to print any page displayed by Ketura, and it provides printer-friendly versions of a number of pages. You may also save information in tables in CSV or XML format for processing by another tool such as a spreadsheet program.

Priority (of issues)

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.

To learn more, see Ketura Tour Step 4: Projects and Milestones.


A project is a planned undertaking directed towards achieving a particular goal. In Ketura, projects comprise a sequence of milestones.

For more information, see Ketura Tour Step 4: Projects and Milestones.


Related issue

One issue can be linked to others by adding other issues as related issues. Related issues can be used to associate issues that share characteristics (for example, a related issue might describe another report of the same bug under different circumstances).

There is no hierarchy in issue relationships, which are symmetrical; if issue A is related to issue B then B is also related to A. See Issue Page.



Ketura uses client-side JavaScript in your browser to improve the usability of the pages it presents. Scripting must be enabled in your browser to use Ketura.


You can search for issues using words found in their summaries, descriptions and comment histories. In an advanced search, additional criteria, such as the user to whom the issue must be assigned, may be defined. Learn more.


From the time when a user logs on to the Ketura System, the user establishes a Ketura session. A session may be terminated either by logging off or after a period of inactivity.


See Issue severity.


See Issue state.

State transition

See Workflow.

Subtopics (or topic versions)

Each topic can have one or more subtopics. Each issue can be associated with a particular subtopic. Learn more.

System administrator

The System Administrator is a user with responsibility for configuring and maintaining the Ketura system. Each Ketura instance has a defined system administrator, who may change the Ketura permissions to allow other users varying access to the system, and otherwise configure the system.



Ketura presents much of its information in the form of tables.


A task is an item of work for an issue, possibly assigned to a particular user. To learn more about tasks, see Ketura Tour Step 3: Tasks.

Task set

Workflow can be used to define the tasks that must be completed for an issue to be resolved. This is done by specifying a set of tasks called Task sets that should be added to the issue when it enters a particular state. Each task in the task set can be assigned to a particular person by default, but can be reassigned if desired. See workflow for more information.



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.



Weights are associated with each Issue Severity to represent the relative importance (from the perspective of the person whose report or request caused an issue to be created) of the severity. For example, the severity type “Cosmetic” might be accorded a weight of 10, whereas a severity type “Critical” might be accorded a weight of 100.

Work done

Work done is the total amount of work that has been undertaken thus far on a task, issue, milestone or project. This is calculated from the information recorded in users’ work journals.

To learn more about work estimates, see Ketura Tour Step 3: Tasks.

Work entry

A work entry represents a period of time spent on a task and is kept in a work journal.

Work journal

A work journal is a historical record of the work effort spent by a user on individual tasks. Each user has his or her own work journal where work entries can be added, updated or deleted. Each work entry represents a period of time spent on a task. Learn more.


Workflow refers to the states and state transitions through which an issue must pass. Ketura allows the states and their transitions to be defined so that an issue progresses through the desired workflow. For example, a company’s quality management system may require that issues submitted by customers are analyzed first by a customer support representative who then (if appropriate) assigns the issue to the manager for a topic who, in turn, would assign the issue to someone for action. Ketura enables such workflows to be automated.

To learn more about workflow, see Ketura Tour Step 8: Workflow.

Work timer

A work timer allows a user to record a period of time against a task by the use of Start and Stop buttons.



XML stands for Extensible Markup Language, a way of representing as text data such as that in the Ketura database. XML is a useful representation of the data because it can be processed very easily by computer programs.

When you use Ketura to save the contents of tables in XML format, each row appears as the contents of an XML<kt:record> element; within the row, each field (column) appears within a <ktd:item name="column"> element, where column corresponds to the name of the column. The table data is enclosed in a single <kt:recordset> element. Any date filtering you may have applied to a table, but generally not other types of filter, is honoured in the XML output.

More information about XML is available at