Item types#
wsman sysman sysadmin
Every item has a type such as “Milestone”, “Bug report” or “Action item”. For each item type you configure your own forms, permissions and workflows. After the initial installation, Allegra ships with a range of item types.
You rename the bundled item types or remove them if you do not need them. The following sections explain the meaning of the suggested item types.
Project and task management#
The following are suitable for general project and task management:
Task: Tasks are planned — with a start and end date. They often have a budget. Tasks carry the “Task” type flag. Only tasks can be synchronized with MS Project files.
Action item: Unlike tasks, action items are not planned — they arise ad hoc in meetings or through external events. They usually have a due date but no budget. Keep tasks and action items separate — that is, not in the same hierarchy tree.
Helpdesk and service management (ITIL)#
The following item types, modeled on the ITIL standard, are suitable for helpdesk and service management:
Ticket: in general the report of an incident, a question or a request for support.
Problem: the cause of one or more incidents. Not every problem leads to an incident — a server crash after office hours is a problem, but it does not become an incident until the next morning, if it has not been resolved by then. An incident can make a problem visible.
Incident: an unplanned disruption or impairment of a service, triggered by a problem. Only the impairment of operations turns the problem into an incident — so outages outside business hours or during maintenance work do not count.
General document management and wiki#
The following are suitable for managing wiki documents — such as requirements documents, meeting minutes or project proposals:
Document folder: a folder for organizing documents in the wiki.
Document: any document in the wiki, made up of document sections.
Document section: a section of a document; it can itself contain sections.
Document folders, documents and document sections are usually invisible in other perspectives.
Agile project management (Scrum)#
The following are suitable for projects run with Scrum:
Epic: a high-level requirement description. You can also represent epics as wiki documents.
User story: a specific requirement description. You can also represent user stories as wiki documents or as sections in wiki documents.
Task: a task that arises from implementing a user story.
Problem report: a bug that occurred while implementing a user story or a task.
Requirements management#
The following are suitable for requirements management in the wiki:
Requirements: a document with links to requirements in the task management perspective.
Document section: a section of a requirements document; it can itself contain sections.
Requirement: a single requirement, referenceable in several requirements documents.
Meeting management#
The following are suitable for meeting agendas and minutes in the wiki:
Document folder: a folder for organizing meeting minutes in the wiki.
Meeting: a document with links into task management.
Agenda item: agenda items collected in task management.
Action item: open points from a meeting that are managed further in task management.