Workspace types

sysman sysadmin

Many organizations run similar projects with similar configurations again and again. Instead of copying that configuration every time, you describe it once in a workspace type. A workspace inherits its configuration from a matching workspace type. If you change a workflow on the workspace type, for example, the change takes effect for all workspaces of that type.

Example: For developing electromechanical systems, you create separate workspace types for electronics, mechanics and software. The mechanical part needs no releases, the electronics need two test versions and one production version, and the software needs full release management, a backlog and sprints.

For a workspace type, you configure the following properties:

• Workspace type category: “Standard”, “Helpdesk” or “Scrum”, depending on your needs.

• Releases and phases: required for Scrum, helpful for software projects (version tracking, sprint management).

• Version management: connects Git or GitLab repositories. Especially relevant for software projects.

• Efforts: assign planned and actual time and cost efforts to items.

• Hours per working day: define the default working time as a fallback when workspaces have no value of their own.

In addition, you configure:

• available item types

• states per item type

• available priorities

• available severities

• permissible workspace types for sub-workspaces

• available roles

• item attributes

• forms

• workflow assignments

You manage workspace types under Administration > Workspaces > Workspace types.

Click Add to create a new workspace type. In the navigation (column A), select a workspace type to edit it.

Click Save in the toolbar to store your changes.

Assigning item types

Define which item types are available in workspaces of this type.

Drag the item types you want from right to left. An empty left-hand list means that all item types are available.

For how to add or change item types, see Managing item types.

Assigning states

Define which states are available for each item type. A milestone, for example, only needs “open” and “passed”, whereas a problem report needs more states.

Tip

Use only the states you really need. A state is worthwhile when items dwell in it for a long time or when the workflow requires the distinction.

Drag the states you want from right to left. An empty left-hand list means that all states are available.

For how to add or change states, see Managing item statuses.

Assigning priorities

Define which priorities are available. You set this per item type.

Drag the priorities you want from right to left. An empty left-hand list means that all priorities are available.

For how to add or change priorities, see Managing priorities.

Assigning severities

Define which severities are available. You set this per item type.

Drag the severities you want from right to left. An empty left-hand list means that all severities are available.

For how to add or change severities, see Managing severities.

Assigning sub-workspace types

Define which workspace types are permissible as sub-workspaces of this workspace type — for instance, that a helpdesk workspace may only contain helpdesk sub-workspaces.

Drag the permissible workspace types from right to left. An empty left-hand list means that all workspace types are permissible.

Customizing item attributes

Item attributes are defined globally. Here you override the configuration for a workspace type — for instance, to use selection lists specific to that workspace type.

For managing custom fields, see Item attributes.

Assigning forms

Define custom forms specifically for this workspace type (see Creating forms).

Assigning workflows

You assign workflows to item types in the selected workspace type (see Workflows).