Tickets
The ticketing system within Centurion ERP is common to all ticket types. The differences are primarily fields and the value of fields.
Features
-
Commenting
-
Linked Items to ticket
-
Milestone
-
Project
-
Related Tickets
-
Slash commands
-
Ticket Types:
-
Changes
-
Incidents
-
Problems
-
Request
-
Project Task
-
Commenting
Comment types are:
-
Standard All Ticket types
-
Notification Change, Incident, Problem, Project Tasks and Request tickets.
-
Solution Change, Incident, Problem, Project Tasks and Request tickets.
-
Task Change, Incident, Problem, Project Tasks and Request tickets.
Slash Commands
Slash commands are a quick action that is specified after a slash command. As the name implies, the command starts with a slash /
. The following slash commands are available:
-
Linked Item
/link
-
Related
/blocked_by
,/blocks
and/relate
-
Time Spent
/spend
,/spent
When using slash commands, there is only to be one slash command per line. All slash commands support reference stacking (more than one reference) as long as they are separated by a space. i.e. /<command> $<model>-<pk> $<model>-<pk> $<model>-<pk>
Time Spent
The command keyword is spend
and you can also use spent
. The formatting for the time
after the command, is <digit>
then either h
, m
, s
for hours, minutes and seconds respectively.
Valid commands are as follows:
-
/spend 1h1ms
-
/spend 1h 1m 1s
For this command to process the following conditions must be met:
-
There is a
<new line>
(\n
) char immediatly before the slash/
-
There is a
<space>
char after the command keyword, i.e./spend<space>1h
-
Optional
<space>
char between the time blocks.
Linked Items
Link an item to the current ticket. Supports all ticket
relations: blocked by, blocks and related.
The command keyword is link
along with the model reference, i.e. $<type>-<number>
.
Valid commands are as follows:
-
/link $device-1
-
/link $cluster-55
You can also stack model references. i.e. /link $device-1 $cluster-55 $software-2254
Available model types for linking are that same as exists for model references. Please see the markdown documentation:
For this command to process the following conditions must be met:
-
There is a
<new line>
() char immediatly before the slash
/
-
There is a
<space>
char after the command keyword, i.e./link<space>$device-101
Related Tickets
Add to the current ticket a relationship to another ticket. Supports all ticket
relations: blocked by, blocks and related.
The command keywords are relate
, blocks
and blocked_by
along with the ticket
reference, i.e. #<ticket-number>
.
Valid commands are as follows:
-
/relate #1
-
/blocks #1
-
/blocked_by #1
You can also stack ticket references. i.e. /relate #1 #10 #500
For this command to process the following conditions must be met:
-
The slash
/
is the first character on the line -
There is a
<space>
char after the command keyword, i.e./relate<space>#1
Ticket Types
Centurion ERP has the following ticket types available:
-
Request
-
Incident
-
Change
-
Problem
As we use a common model for ALL ticket types. Effort has been made to limit fields showing for a ticket type that it does not belong. If you find a field displayed that does not belong to a ticket, please create an issue.
Ticket Comments
Within Centurion ERP the ticket comment model is common to all comment types. As with tickets the differences are the available fields, which depend upon comment type and permissions.
Comment types are as follows:
-
Action
-
Comment
-
Solution
-
Notification
Action
An action comment is for the tracking of what has occured to the ticket.
Comment
This is the default comment type and is what would be normally used.
Solution
This type of comment is an ITSM comment and is used as the means for solving the ticket.
Notification
This type of comment is intended to be used to send a notification to subscribed users.
About:
This page forms part of our Project Centurion ERP.
Page Metadata
Version: ToDo: place files short git commit hereDate Created: 2024-08-23
Date Edited: 2025-03-19
Contribution:
Would You like to contribute to our Centurion ERP project? You can assist in the following ways:
- Edit This Page If there is a mistake or a way you can improve it.
- Add a Page to the Manual if you would like to add an item to our manual
- Raise an Issue if there is something about this page you would like to improve, and git is unfamiliar to you.
ToDo: Add the page list of contributors