Article: AN0002497Updated: 19.01.2024
Description
Class contains the Task entity of the IT (CMDB) model solution.
Location and referencing
Location |
Code |
Name |
Model |
it |
IT |
Class |
tasks |
Task |
Parent class |
|
|
Child classes |
|
|
Script object |
OG.ClassDef.GetByCode(OGModel.Id, 'tasks')
OG.ClassDef.GetByCode('it', 'tasks') |
Columns
Overview of class columns (excl. system columns):
Code |
Name |
Type |
Link information |
Description |
affected-CI |
Affected CI |
Class link (multiple) |
Configuration items |
Configuration items that will be affected by the task. |
area |
Area |
Class link (simple) |
Area |
Area, into which the task belongs. |
artifact |
Artifact |
Class link (simple) |
Artifacts |
Artifact, that the task should deliver. |
cl_tasks |
Workflow request - Tasks |
Revers class link (multiple) |
Workflow request (revers) |
Automatically created column. |
cl_tasks_2 |
Catalogue request - Task |
Revers class link (multiple) |
Requests:Catalogue request
(revers) |
Automatically created column. |
cl_tasks_3 |
Time stamps - Task |
Revers class link (multiple) |
Time marks
(revers) |
Automatically created column. |
cl_tasks_4 |
Task - Parent |
Revers class link (multiple) |
Task
(revers) |
Automatically created column. |
cl_tasks-2 |
History - Task |
Revers class link (multiple) |
Time sheets
(revers) |
Automatically created column. |
cl-tasks |
Task - Depending on |
Revers class link (multiple) |
Task
(revers) |
Automatically created column. |
cl-tasks-2 |
Service tickets - Tasks |
Revers class link (multiple) |
Service tickets
(revers) |
Automatically created column. |
cl-tasks-3 |
Changes - Within task |
Revers class link (multiple) |
Changes
(revers) |
Automatically created column. |
code |
Code |
Text |
|
Code of the task to use in scripting or other references. It should not be changed. |
customer |
Customer |
User link (simple) |
User |
User for whom the task is developed. |
deadline |
Deadline |
Date and time |
|
Target date for the task resolution. |
depending-on |
Depending on |
Class link (multiple) |
Task |
Other tasks on which task completion is depending. |
description |
Description |
Text |
|
Description of the task. Long text in the mode of added comments. |
escalate |
Escalate |
True/untrue |
|
Indication whether the task is escalated. |
files |
Files |
File |
|
Attachments to the task. |
change_request |
Change request (RFC) |
Class link (simple) |
Change request (RFC) |
Change request to which the task relates. |
md_estimate |
Mandays estimate |
Decimal |
|
Estimate of mandays, that the task completion will require. |
name |
Name |
Text |
|
Name of the task, a brief description of what has to be performed. |
parent |
Parent task |
Class link (simple) |
Task |
Parent task. |
project |
Project |
Class link (simple) |
Project |
Project, into which the task belongs. |
reflected-in |
Reflected in |
Class link (multiple) |
Configuration items |
Configuration items in which the task completion was reflected. |
release |
Release |
Class link (simple) |
Release |
Release, to which the task relates. |
request |
Detailed request |
Class link (simple) |
Detailed request |
Detailed request, to which the task relates. |
resolution |
Resolution |
Text |
|
Description, how the task was resolved. |
solution_team |
Solution team |
Class link (simple) |
Solution team |
Solution team, to which the task was assigned. |
solver |
Solver |
User link (simple) |
User |
Solver, to whom the task was assigned. |
solvers |
Collaboration |
User link (multiple) |
User |
Users, that collaborate on the task with the chief Solver. |
stage_settings |
Stage |
Class link (simple) |
Stage settings |
Project stage, to which the task relates. |
status |
Status |
Class link (simple) |
Task status |
Task status. |
user_story |
User story |
Class link (simple) |
User story |
User story, to which the task relates. |
wbs_item |
WBS item |
Class link (simple) |
WBS |
Work Breakdown Structure item, to which the task relates. |
Rules
Code |
Event type |
Action type |
Order |
Description |
inic_project |
Before new record detail display |
Start a script |
10 |
Fills in project, if the task is initiated according to a Change request (RFC). |
colour_new |
Before existing record list display |
Set formatting |
10 |
Colour - New |
colour_work_in_progress |
Before existing record list display |
Set formatting |
20 |
Colour - Work in progress |
colour_resolved |
Before existing record list display |
Set formatting |
30 |
Colour - Resolved |
status_as_new |
Before new record detail display |
Set or calculate value |
40 |
Set Status as New |
podbarveni_assigned |
Before existing record list display |
Set formatting |
50 |
Colour - Assigned |
new_notification |
After new record save |
Send notification |
60 |
NEW - Notification to solver |
upd_notification |
After existing record save |
Send notification |
70 |
UPD - Notification to solver |
upd_notification_customer |
After existing record save |
Send notification |
80 |
UPD - Notification to customer |
upd_escalate |
After existing record save |
Start a script |
100 |
Escalation to superior |
upd_check_planned_capacities |
Before existing record save |
Start a script |
110 |
Check of planned capacities |
check_planned_capacities |
Before new record save |
Start a script |
120 |
Check of planned capacities |
time_mark_upd |
Before existing record save |
Start a script |
200 |
Time stamps - change in specified columns |
set_state_assigned_ins |
Before new record save |
Start a script |
1000 |
Setting Status Asigned when the solver is defined |
set_state_assigned_upd |
Before existing record save |
Start a script |
1010 |
Setting Status Asigned when the solver is defined |
Quick filter
In order users can easily filter the records some columns are selected for a Quick filter.
Buttons
Icon |
Code |
Name |
Order |
Description |
|
takeover |
Take over |
100 |
Assigns the current user to the column Solver and saves the record. |
Master/detail relations
Code |
Column |
Placement |
Bookmark name |
Type |
code_242 |
Changes - Within task |
Below |
elated changes |
Reference to class |
code_248 |
Service tickets - Tasks |
Below |
Service tickets |
Reference to class |
code_321 |
Catalogue request - Task |
Below |
Catalogue requests |
Reference to class |
code_314 |
History - Task |
Below |
Time sheet |
Reference to class |
time_marks |
Time stamps - Task |
Below |
Time marks |
Reference to class |
subtasks |
Task - Parent |
Below |
Subtasks |
Reference to class |
Potential improvements
You can improve the solution according to your needs. Here are some tips.
Add new columns
Add new columns, if you are going to need them.
Add buttons
Add new buttons to automate edits that you would otherwise make one at a time.
Set permissions based on organizational structures
If you need to separate the visibility of tasks according to the teams working on them, use Organizational Structures. You can use them to control permissions on individual records. You'll share a single task repository, but at the same time assign permissions only to the tasks that users need to see.
Time operations
Nastavte Časové oprace, které budou hlídat termín úkolu a posílat připomenutí pro dokončení úkolu nebo provádět eskalace, pokud úkol nebude včas řešen.
Set up Time operations to monitor a task's deadline and send reminders to complete the task or escalate if the task is not completed on time.