Code Lists

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== Code Lists – Ticket Management ======

<WRAP 100%>
<WRAP 520px left>
{{:cs:tickets:ciselniky_mu.png?direct&500|Code List – Ticket Management}}
</WRAP>
This section of the project settings contains all code lists available in the Ticket Management module that can be defined or modified by the project administrator.\\
These include:
  * Ticket Categories
  * Assignees Rule
  * Approvers Rule
  * Labels
<WRAP clear />
</WRAP>
\\
===== Ticket Categories =====
 
<WRAP 100%>
<WRAP 570px left>
{{:cs:tickets:kategorie_ukolu2.png?direct&550|Ticket Categories}}
</WRAP>
**__Ticket Categories__** is a code list used to divide tickets into basic groups according to the subject matter they concern. This code list is predefined by default, and users select an item when creating a new ticket or editing an existing one.\\
The administrator can modify or delete the predefined items using the icons at the end of each row, or add new ones using the {{:cs:diary:btn_pridat.png?nolink|+ Add}} button.
<WRAP info round 50%> 
Categories that are already used in a ticket cannot be deleted. They can only be edited.
</WRAP>
The **two-letter abbreviation** is used to make it easier to identify locations where the category is represented by an icon containing this abbreviation. We therefore recommend choosing an intuitive abbreviation.
<WRAP clear />
</WRAP> 
\\

===== Rules =====

<WRAP 100%>
<WRAP 600px left>
{{:cs:tickets:pravidla2.png?direct&580|Rules}}
</WRAP>
A **__Rule__** is a set of conditions under which the **Assignees** and/or **Approvers** field is automatically populated when a ticket is created.\\ A user with administrator rights can create different rules for different situations where the responsible persons are clearly defined.\\ This can save a significant amount of time and effort and eliminate uncertainty when creating new tickets.\\ Rules can be added gradually, and there is no limit to the number of rules that can be defined.\\ Their **order can be changed in the list** according to their importance or priority (a rule higher in the list takes precedence over a rule below it).
<WRAP clear />
</WRAP> 
\\
<WRAP 100%>
<WRAP 300px left>
{{:cs:tickets:nove_pravidlo.png?direct&280|New Rule}}
</WRAP>
<WRAP 300px right>
{{:cs:tickets:nove_pravidlo2.png?direct&280|Rule Definition}}
</WRAP>
A **__New Rule__** is defined by selecting **one or more persons in the Assignees or Approvers field**, depending on which tab the rule is being created in. Persons are selected from a list containing all Project Team Members. If the required person is not listed, they must first be added to the project's Project Team.\\
__The rule conditions are defined by selecting:__
  * **Category** - the list of categories is defined in the adjacent tab
  * **Project Parts** - the list is based on the Project Parts and Drawings tab, which must first be defined by the administrator
  * **Drawings** - drawings must be uploaded in the Project Parts and Drawings tab before they can be selected
__Example__ \\ The image on the right shows the following rule: If a ticket is assigned to the category Non-Conformities, Defects and Incomplete Works, OR Inspection Days and Meetings, AND at the same time concerns either Project Part SO 02 - Access Road, OR SO 03 - Utility Networks, OR SO 04 - Landscaping, and any drawing from any of these three parts, the **Assignees** field will be automatically populated with the names Iva Černá and Tomáš Novák. These names can then be individually supplemented with additional people or changed directly in the ticket.\\ If the ticket concerned Project Part SO 02 but had, for example, the category Inspections and Tests, the condition would not be met and the rule would not be applied.
<WRAP clear />
</WRAP> 
\\

===== Labels =====

<WRAP 100%>
<WRAP 520px left>
{{:cs:tickets:stitky2.png?direct&500|Labels}}
</WRAP>
Tickets can be organized not only by assigning them to a category, but also according to individual parameters by adding a label.\\ 
This code list is empty by default, and the administrator can define labels according to the specific characteristics and requirements of the project.\\ 

**For each label, a color, name, and optionally a description can be specified.** Color highlighting makes it easier to identify and visually categorize tickets at a glance.\\

**Labels** are displayed **in the ticket list** (after adding the relevant column to the view), and tickets can be **filtered** by them.\\

In the Ticket Kanban, labels are displayed automatically, but tickets cannot be filtered by them.  
<WRAP clear />
</WRAP> 
\\