Manage Item Types¶
Each item belongs to an item type, such as “improvement proposal”, “milestone” or “problem message”. You can delete available item types, change them, or add new ones. Item types are defined globally. However, you can define for each workspace type which item types are available for a workspace.
First of all, you must be logged in as a system manager or system administrator.
You use different item types when you:
Need items with different input screens
Need to assign different workflows to items
Need to restrict access to specific items based on roles
Want to be able to distinguish items, such as a problem message from an error (not every problem message is based on an error)
Allegra comes with a set of default item types. You can delete or rename the types you don’t need. When you delete an item type you are using, the items of that type are assigned to a replacement type that you can specify.
Item type |
Description |
|---|---|
Task |
Plannable tasks, for example, from a work breakdown structure with many tasks or work packages. For a project manager, it is very tedious to keep track of the status of such a task. With the help of this list and the fact that each $RESPONSIBLE takes care of the status of their work package, the project manager can easily determine the current status of their project and, for example, check for late packages. |
Action Item |
Non-plannable, organization-internal items, e.g., from meetings. |
Ticket |
Non-scheduled items created outside the organization, e.g., support requests. |
Problem Report |
Someone has a problem with something that is not specified. This could be a know-how problem, a user interface problem, or a bug. |
Meeting |
In a well-managed project, there is a work breakdown structure with many work packages. It is very tedious for a project manager to keep track of the status of such work packages. With the help of this list and the fact that each $RESPONSIBLE takes care of the status of their work package, the project manager can easily find out the current status of their project and, for example, check for late packages. |
Requirement |
A list of requirements that enables requirements engineering and tracing. Since attachments can be added to each item, you can add images, source code, or other documents to a requirement. |
Document Folder |
Documents can be organized into folders. |
Document |
A document is used for the Wiki app. It is essentially a single Wiki page and can be exported to a Word document based on a template. |
Document section |
A document section is a subordinate part of a document. It can be exported to a Word document as a paragraph. Document sections can contain other document sections. |
The list of available item types is global. You can, however, define for each workspace type which item types should be available in workspaces or projects of this type (see Workspace Types).
Go to Administration > Customize > Lists > Global Lists > Item Type.
You can now modify, add or delete an item type. You can assign an icon (16 x 16 px, GIF, SVG or PNG format) to each item. You can also assign a CSS style to each item, which is used to format items in the Item Navigator. Each item type has a type flag. This has the following meaning:
General: This is the default type for items that do not require any special behavior.
Task: Only item types with this type flag appear in the Gantt chart. Example: Task.
Document Folder: Item types with this type flag appear as folders in Wiki. Example: Document folder.
Document: Item types with this type flag appear as documents in Wiki. Examples: Document, Requirements, Meeting.
Document section: Item types with this type flag appear as sections in tasks of type “Document” such as meetings or requirements.
Epic: Type flag for Epics.
User Story: Type flag for User Stories.
Attention
If you rename an entry, the change may not be visible in the user interface. This happens if you have specific localizations for the selection entries, which is the case for all predefined entries. In this case, the localized values are displayed instead and not the label that you define here.