Item Types¶
Items have a type, such as “milestone”, “error message”, or “action item”. For each item type, you can configure your own input masks, authorizations, and workflows. After the initial installation, the system offers you a number of item types.
You can rename or remove the supplied item types if you do not need them. The next sections explain the meaning of the proposed item types.
Project and Task Management¶
The following item types are useful for general project and task management:
Task: Tasks are scheduled and have a start date and an end date. Often, they also have a budget. Tasks have the type flag “Task”. Only tasks can be synchronized with MS Project files.
Action Item: Unlike tasks, action items are not planned, but arise ad hoc in meetings or due to external events. Action items usually have an optional completion date, but no budget. It is recommended to keep tasks and action items separate from each other, i.e. not to place them in the same hierarchy tree.
Helpdesk and Service Management (ITIL)¶
The following item types are useful for Helpdesk and Service Management. They are derived from the ITIL standard:
Ticket: In very general terms, tickets represent the reporting of an incident, a question or a request for assistance.
Problem: Problems present the cause of one or more incidents. Not every problem leads to an incident. A server crash after hours is a problem, but it doesn’t become an incident until it hasn’t been fixed the next morning when people are back in the office. An incident can make a problem visible.
Incident: Incidents represent the unplanned disruption or degradation of a service caused by a problem. To become an incident, the service outage must affect items. Thus, outages outside of operating hours or maintenance would not count as incidents.
General Document Management and Wiki¶
The following item types are useful for managing documents held in the Wiki view, such as requirements documents, meeting minutes, and project proposals. Document folders, documents, and document sections are normally invisible in other perspectives.
Document Folder: A folder used to organize documents in the Wiki view
Document: Any document in the Wiki view, consisting of document sections
Document Section: A section in a document, which can itself contain sections
Agile Project Management (Scrum)¶
The following item types are used for projects according to the Scrum methodology:
Epic: A rough requirement description
User Story: A specific requirement description
Task: A task that arises while implementing a user story
Problem Report: Errors that occur during the implementation of a user story or task
Requirements Management¶
The following item types are useful for managing documents held in the Wiki view:
Requirements: A document that contains links to requirements in the task management perspective
Document Section: A section in a requirements document that might itself contain sections
Requirement: A single requirement that can be referenced in multiple requirements documents
Meeting Management¶
The following item types are useful for managing meeting agendas and minutes in the Wiki view:
Document Folder: A folder for organizing meeting minutes in the Wiki view
Meeting: A document with links into task management
TOP: Agenda items collected in the Task Management perspective
Action Item: Open items from a meeting that are managed in the Task Management view
Test Management¶
The following item types are useful for managing tests:
Test specification
Test case
Test protocol
Test suite
Test case
Test run