General principles
Goal of issues
Issues are escalations, notes or notifications that start at the source and help to provide structure. They provide a basis for communication and help make reporting scalable. They include a chat functionality where insights from others can be shared.
Standard fields to issues
Mandatory fields
Category (mandatory) - Each issue belongs to a certain category
Title (mandatory) - Each issue has a title
Priority (mandatory) - Each issue has a priority. Default value is "low"
Equipment (mandatory) - Each issue need to be linked to an equipment
Optional fields
Description (optional) - Meer details kunnen weggeschreven worden in de omschrijving
Assignees (optional) - An issue can be assigned to users or workstations. When one selects the user category, a shortcut key “Assign to me” will appear. The selection lists of both users and workstations can be limited using advanced flows. Because issues that are not assigned rarely get closed, an empty selection of assignees will ask you whether you want to close the issue automatically.
Deadline (optional) - A deadline can be given to an issue. This is a date, possibly supplemented with a time (hour). There are some shortcuts keys available, namely “Tomorrow”, “Next week”, “Next month”
Status
There are three predefined status categories that can be given to an issue
Open - An action is required by someone
Closed - Completed and no further follow-up required
Canceled - Not processed, but no further follow-up required
Prerequisites to get started
Category- At least one category needs to be configured via
Settings›Issues›CategoriesEquipment- At least one equipment needs to be configured via
Settings›Organization›Equipment
Last updated