RTIR
Request Tracker for Incident Response is a ticketing system which provides pre-configured queues and workflows designed for incident response teams.
Case Management · RTIR
Details
| ID | RTIR |
|---|---|
| Provider | Open Source |
| Category | Case Management |
| From Version | 5.0.0 |
| Docker Image | demisto/python3:3.12.13.10116658 |
| Supported Modules | Agentix XSIAM |
README
Use the Request Tracker for Incident Response (RTIR) integration to manage tickets and incidents.
This integration was integrated and tested with RTIR v4.4.2, using the SDK python-rtir v1.0.11.
Use Cases
- Create new tickets.
- Resolve existing tickets.
- Search for tickets using filters.
- Edit tickets.
- Get ticket data.
Known Limitations
- This integration does not support the lifecycle
countermeasures. - Custom fields cannot be created through this integration, but custom fields created on RTIR can be filled when creating a new ticket.
Configure RTIR on Cortex XSOAR
- Navigate to Settings > Integrations > Servers & Services.
- Search for RTIR.
- Click Add instance to create and configure a new integration instance.
- Name: A textual name for the integration instance.
- Server URL (for example: https://192.168.0.1)
- Username
- Password
- Token
- Certificate
- Private Key
- Trust any certificate (not secure)
- Use system proxy settings
- Use system proxy settings
- Fetch incidents
- Fetch incidents with priority greater or equal to
- Fetch incidents of the following status
- Incident type
- Referer request header
- Click Test to validate the URLs and token.
Fetched Incidents Data
The integration fetches newly created tickets. The tickets are fetched by ID in ascending order, starting from 0 at the first fetch. The fetch is filtered by priority and status, which can be set in the integration settings. The initial fetch interval is one minute.
The following data is fetched for each ticket:
- General ticket information: ID, priority, created date, subject, queue, custom fields, and so on.
- Ticket history.
- Ticket attachments.
Commands
You can execute these commands from the Cortex XSOAR CLI, as part of an automation, or in a playbook. After you successfully execute a command, a DBot message appears in the War Room with the command details.
- Create a new ticket: rtir-create-ticket
- Search for tickets: rtir-search-ticket
- Close a resolved ticket: rtir-resolve-ticket
- Edit a ticket: rtir-edit-ticket
- Get the history of a ticket: rtir-ticket-history
- Get ticket details: rtir-get-ticket
- Get ticket attachments: rtir-ticket-attachments
- Add a comment to a ticket: rtir-add-comment
1. Create a new ticket
Creates a new ticket in RFIR.
Base Command
rtir-create-ticket
Input
| Argument Name | Description |
| queue | Where to create the ticket. |
| subject | Subject of the ticket. |
| requestor | Email address of the requester. |
| cc | Sends a carbon-copy (cc) of this update to a comma separated list of email addresses. These people will also receive future updates. |
| admin-cc | Sends a carbon-copy (cc) of this update to a comma separated list of administrative email addresses. These people will also receive future updates. |
| owner | Ticket owner |
| status | Ticket status |
| priority | Ticket priority |
| text | The ticket content |
| initial-priority | Initial priority of ticket |
| final-priority | Final priority of ticket |
| member-of | Ticket MembersOF links |
| members | Ticket Members links |
| attachment |
Comma separated list of entry IDs of attachment to add to the ticket (for example: entryID1,entryID2). |
| customfields |
Ticket custom fields, in the following format: field1=value1,field2=value2. For example: IP=8.8.8.8,HowReported=Email. Note: This command does not create custom fields, these should be created on RTIR. |
Context Output
| Path | Description |
| RTIR.Ticket.ID | Ticket ID. |
| RTIR.Ticket.InitialPriority | Ticket initial priority 0-100). |
| RTIR.Ticket.Priority | Ticket priority (0-100). |
| RTIR.Ticket.FinalPriority | Ticket final priority (0-100). |
| RTIR.Ticket.Owner | Ticket owner. |
| RTIR.Ticket.Subject | Ticket subject. |
| RTIR.Ticket.Creator | Ticket creator. |
Command Example
!rtir-create-ticket subject=NewTicket queue="Incident Reports" priority=70 requestor=root@localhost customfields="IP=8.8.8.8,How Reported=Email"
Raw Output
Ticket 121 was created successfully.
Context Example
{
"RTIR": {
"Ticket": {
"CF_How Reported": "Email",
"CF_IP": "8.8.8.8",
"Priority": 70,
"Requestor": "root@localhost",
"Subject": "NewTicket"
}
}
}
2. Search for tickets
Searches for tickets in RTIR using specified filters.
Base Command
rtir-search-ticket
Input
| Argument Name | Description |
| ticket-id | Ticket ID |
| subject | Ticket subject |
| queue |
CSV list of ticket queues. For example: General,Incident reports,Incidents |
| status | Ticket status |
| creator | Ticket creator |
| priority-equal-to | Ticket priority (range 0-100) |
| priority-greater-than | Ticket priority (range 0-100) |
| created-after |
Date after which the ticket was created, in the following format: YYYY-MM-DD. For example: 2011-02-24 |
| created-on |
Date the ticket was created, in the following format: YYYY-MM-DD. For example: 2011-02-24 |
| created-before |
Date before which the ticket was created, in the following format: YYYY-MM-DD. For example: 2011-02-24 |
| owner | Ticket owner |
| due |
Ticket due date, in the following format: YYYY-MM-DD. For example: 2011-02-24 |
Context Output
| Path | Description |
| RTIR.Ticket.ID | Ticket ID. |
| RTIR.Ticket.State | Ticket state. |
| RTIR.Ticket.Creator | Ticket creator. |
| RTIR.Ticket.Subject | Ticket subject. |
| RTIR.Ticket.Created | Ticket creation date. |
| RTIR.Ticket.Priority | Ticket priority (0-100). |
| RTIR.Ticket.InitialPriority | Ticket initial priority (0-100). |
| RTIR.Ticket.FinalPriority | Ticket final priority (0-100). |
| RTIR.Ticket.Queue | Ticket queue. |
| RTIR.Ticket.Owner | Ticket owner. |
| RTIR.Ticket.IP | Ticket custom field - IP address. |
| RTIR.Ticket.HowReported | Ticket custom field - How ticket was reported. |
| RTIR.Ticket.Customer | Ticket custom field - Customer. |
Command Example
!rtir-search-ticket queue=General created-after=2018-07-10 priority-greater-than=10 status=new
[
{
"Created": "Thu Jul 12 03:56:06 2018",
"Creator": "root",
"Due": "Not set",
"FinalPriority": "0",
"InitialPriority": "0",
"LastUpdated": "Thu Jul 12 03:56:06 2018",
"Owner": "Nobody",
"Priority": "12",
"Queue": "General",
"Requestors": [
""
],
"Resolved": "Not set",
"Started": "Not set",
"Starts": "Not set",
"Status": "new",
"Subject": "unbelievable",
"TimeEstimated": "0",
"TimeLeft": "0",
"TimeWorked": "0",
"Told": "Not set",
"id": "ticket/21"
}
}
]
Context Example
{
"RTIR": {
"Ticket": {
{
"Created": "Thu Jul 12 03:56:06 2018",
"Creator": "root",
"FinalPriority": 0,
"ID": 21,
"InitialPriority": 0,
"Owner": "Nobody",
"Priority": 12,
"Queue": "General",
"State": "new",
"Subject": "unbelievable"
}
}
}
3. Close a resolved ticket
Closes a ticket that has been resolved.
Base Command
rtir-resolve-ticket
Input
| Argument Name | Description |
| ticket-id | Ticket ID of the ticket to close. |
Context Output
| Path | Description |
| RTIR.Ticket.ID | Ticket ID. |
| RTIR.Ticket.State | Ticket state. |
Command Example
!rtir-resolve-ticket ticket-id=121
Raw Output
Ticket 121 was closed successfully.
Context Example
{
"RTIR":{
"Ticket":{
"ID":"121",
"State":"resolved"
}
}
}
4. Edit a ticket
Edit a specific ticket. Ticket ID specifies which ticket to edit.
Base Command
rtir-edit-ticket
Input
| Input Parameter | Description |
| ticket-id | Ticket ID of the ticket you want to edit. |
| subject | Modified ticket subject. |
| priority | Modified ticket priority (0-100). |
| final-priority | Modified ticket final priority (0-100). |
| owner | Modified ticket owner. |
| status | Modified ticket status. |
| member-of | Modified ticket MembersOF ID |
| members | Modified ticket Members ID |
| depends-on | Modified ticket DependedOn ID |
| depended-on-by | Modified ticket DependedOnBy ID |
| refers-to | Modified ticket RefersTo ID |
| referred-to-by | Modified ticket ReferredToBy ID |
| due |
Modified ticket due date, in the following format: YYYY-MM-DD. For example: 2011-02-24 |
Context Output
| Path | Description |
| RTIR.Ticket.ID | Ticket ID. |
| RTIR.Ticket.FinalPriority | Ticket final priority (0-100). |
| RTIR.Ticket.Priority | Ticket priority (0-100). |
| RTIR.Ticket.Owner | Ticket owner. |
| RTIR.Ticket.State | Ticket state. |
| RTIR.Ticket.Subject | Ticket subject. |
Command Example
!rtir-edit-ticket ticket-id=115 final-priority=100 status=open subject=NewTicketSubject
Raw Output
Ticket 115 was edited successfully.
Context Example
{
"RTIR": {
"Ticket": {
"FinalPriority": 100,
"ID": 115,
"Owner": "root",
"Priority": 0,
"State": "open",
"Subject": "NewTicketSubject"
}
}
}
5. Get the history of a ticket
Get the history of a specified ticket.
Base Command
rtir-ticket-history
Input
| Input Parameter | Description |
| ticket-id | Ticket ID for which to retrieve the history. |
Context Output
| Path | Description |
| RTIR.Ticket.ID | Ticket ID. |
| RTIR.Ticket.History.Content | Ticket history content. |
| RTIR.Ticket.History.Created | Ticket history creation date. |
| RTIR.Ticket.History.Creator | Ticket history creator. |
| RTIR.Ticket.History.Description | Ticket history description. |
| RTIR.Ticket.History.NewValue | Value updated in history transaction. |
Command Example
!rtir-ticket-history ticket-id=1
Raw Output
[
{
"Attachments": [
[
1,
"untitled (4b)"
]
],
"Content": "test\n",
"Created": "2018-07-09 07:25:47",
"Creator": "root",
"Data": "",
"Description": "Ticket created by root",
"Field": "",
"NewValue": "",
"OldValue": "",
"Ticket": "1",
"TimeTaken": "0",
"Type": "Create",
"id": "54"
}
]
Context Example
{
"RTIR": {
"Ticket": {
"History": [
{
"Content": "test\n",
"Created": "2018-07-09 07:25:47",
"Creator": "root",
"Description": "Ticket created by root"
}
],
"ID": 1
}
}
}
6. Get ticket details
Get the details of a specific ticket.
Base Command
rtir-get-ticket
Input
| Input Parameter | Description |
| ticket-id | Ticket ID for which to retrieve details. |
Context Output
| Path | Description |
| RTIR.Ticket.LinkedTo.ID | Linked ticket ID. |
| RTIR.Ticket.ID | Ticket ID. |
| RTIR.Ticket.State | Ticket state. |
| RTIR.Ticket.Creator | Ticket creator. |
| RTIR.Ticket.Subject | Ticket subject. |
| RTIR.Ticket.Created | Ticket creation date. |
| RTIR.Ticket.Priority | Ticket priority (0-100). |
| RTIR.Ticket.InitialPriority | Ticket initial priority (0-100). |
| RTIR.Ticket.FinalPriority | Ticket final priority (0-100). |
| RTIR.Ticket.Queue | Ticket queue. |
| RTIR.Ticket.Owner | Ticket owner. |
| RTIR.Ticket.IP | Ticket custom field - IP address. |
| RTIR.Ticket.HowReported | Ticket custom field - How the ticket was reported. |
| RTIR.Ticket.Customer | Ticket custom field - Customer. |
Command Example
!rtir-get-ticket ticket-id=1
Raw Output
{
"CF.{Customer}": "",
"CF.{How Reported}": "Email",
"CF.{IP}": "8.8.8.8",
"CF.{Reporter Type}": "",
"Created": "Mon Jul 09 03:25:47 2018",
"Creator": "root",
"Due": "Thu Jul 19 07:47:05 2018",
"FinalPriority": "0",
"InitialPriority": "0",
"LastUpdated": "Thu Jul 12 10:20:02 2018",
"Owner": "root",
"Priority": "0",
"Queue": "Incident Reports",
"Requestors": [
""
],
"Resolved": "Not set",
"Started": "Thu Jul 19 00:00:00 2018",
"Starts": "Not set",
"Status": "open",
"Subject": "test",
"TimeEstimated": "0",
"TimeLeft": "0",
"TimeWorked": "0",
"Told": "Not set",
"id": "ticket/1"
}
Context Example
{
"RTIR": {
"Ticket":
"Created": "Mon Jul 09 03:25:47 2018",
"Creator": "root",
"Due": "Thu Jul 19 07:47:05 2018",
"FinalPriority": 0,
"HowReported": "Email",
"ID": 1,
"IP": "8.8.8.8",
"InitialPriority": 0,
"LinkedTo": [
{
"ID": 15
}
],
"Owner": "root",
"Priority": 0,
"Queue": "Incident Reports",
"State": "open",
"Subject": "test"
}
}
}
7. Get ticket attachments
Returns the attachment details of the specified ticket, and the attachment files to download from the War Room.
Base Command
rtir-ticket-attachments
Input
| Input Parameter | Description |
| ticket-id | Ticket ID for which to retrieve attachments. |
Context Output
| Path | Description |
| RTIR.Ticket.ID | Ticket ID. |
| RTIR.Ticket.Attachment.ID | Attachment ID. |
| RTIR.Ticket.Attachment.Name | Attachment file name. |
| RTIR.Ticket.Attachment.Size | Attachment file size. |
| RTIR.Ticket.Attachment.Type | Attachment file type. |
| File.EntryID | Cortex XSOAR entry ID of the attachment. |
Command Example
!rtir-ticket-attachments ticket-id=41
Raw Output
[
{
"ID": 77,
"Name": "pdf.pdf",
"Size": "423.8k",
"Type": "application/octet-stream"
},
{
"ID": 78,
"Name": "SampleTextFile_10kb.txt",
"Size": "9.2k",
"Type": "text/plain"
}
]
Context Example
{
"RTIR": {
"Ticket": {
"Attachment": [
{
"ID": 77,
"Name": "pdf.pdf",
"Size": "423.8k",
"Type": "application/octet-stream"
},
{
"ID": 78,
"Name": "SampleTextFile_10kb.txt",
"Size": "9.2k",
"Type": "text/plain"
}
],
"ID": 41
}
}
}
8. Add a comment to a ticket
Add a textual comment to a specified ticket.
Base Command
rtir-add-comment
Input
| Input Parameter | Description |
| ticket-id | Ticket ID to add a comment to. |
| text | Text of the comment. |
| attachment |
CSV list of attachment entry IDs to add to the ticket. For example: entryID1,entryID2 |
Context Output
There is no context output for this command.
Command Example
!rtir-add-comment text=CommentText ticket-id=113 attachment=1336@cc6f4232-d87e-496e-82b5-6bbeab422243
Raw Output
Added comment to ticket 113 successfully.
Context Example
There is no context example for this command.
9. Add a reply to a ticket
Add a textual reply to a specified ticket.
Base Command
rtir-add-reply
Input
| Input Parameter | Description |
| ticket-id | Ticket ID to add a comment to. |
| text | Text of the comment. |
| cc |
Email of the user to send the reply. |
Context Output
There is no context output for this command.
Command Example
!rtir-add-reply text=replyText ticket-id=113
Raw Output
Added reply to ticket 113 successfully.
Context Example
There is no context example for this command.
Configuration parameters
server— Server URL (e.g. http://192.168.0.1) (required)credentials— Usernametoken—certificate— Certificateunsecure— Trust any certificate (not secure)proxy— Use system proxy settingsisFetch— Fetch incidentsincidentType— Incident typeincidentFetchInterval— Incidents Fetch Intervalfetch_status— Fetch incidents of the following status:fetch_priority— Fetch incidents with priority greater or equal to:fetch_queue— Queue name to fetch incidents fromreferer— Referer request headerfetch_limit— Fetch incidents limit (the max amount of incidents per fetch iteration)
Commands (9)
-
rtir-add-commentAdd a comment to an existing ticket.
-
rtir-add-replySend a reply from an existing ticket to the user.
-
rtir-create-ticketCreate new ticket on RTIR.
-
rtir-edit-ticketModify a ticket on RTIR.
-
rtir-get-ticketGets the data for a single ticket.
-
rtir-resolve-ticketSets a ticket as resolved on RTIR.
-
rtir-search-ticketSearch for tickets on RTIR.
-
rtir-ticket-attachmentsGets a list of all attachments details and data content related to the ticket.
-
rtir-ticket-historyGets a list of all the history items for a given ticket.
category: Case Management provider: Open Source commonfields: id: RTIR version: -1 sectionorder: - Connect - Collect configuration: - display: Server URL (e.g. http://192.168.0.1) name: server required: true type: 0 section: Connect - display: Username name: credentials required: false type: 9 section: Connect - name: token type: 9 displaypassword: Token hiddenusername: true section: Connect - display: Certificate name: certificate type: 9 required: false section: Connect displaypassword: Private Key - display: 'Trust any certificate (not secure)' name: unsecure type: 8 required: false section: Connect - display: 'Use system proxy settings' name: proxy type: 8 required: false section: Connect - display: 'Fetch incidents' name: isFetch type: 8 required: false section: Collect - display: 'Incident type' name: incidentType type: 13 required: false section: Collect - display: Incidents Fetch Interval name: incidentFetchInterval defaultvalue: '1' required: false type: 19 section: Collect advanced: true - defaultvalue: 'new,open' display: 'Fetch incidents of the following status:' name: fetch_status type: 0 required: false section: Collect - display: 'Fetch incidents with priority greater or equal to:' name: fetch_priority type: 0 required: false defaultvalue: '0' section: Collect - defaultvalue: 'Incident Reports' display: Queue name to fetch incidents from name: fetch_queue type: 0 required: false section: Collect - display: Referer request header name: referer type: 0 required: false section: Collect - defaultvalue: '0' display: Fetch incidents limit (the max amount of incidents per fetch iteration) name: fetch_limit type: 0 required: false section: Collect description: Request Tracker for Incident Response is a ticketing system which provides pre-configured queues and workflows designed for incident response teams. display: RTIR name: RTIR script: commands: - arguments: - defaultValue: General description: Queue where to create the ticket. name: queue - description: Subject of the ticket. name: subject required: true - description: Requestor email address. name: requestor - description: Sends a carbon-copy of this update to a comma-delimited list of email addresses. These people will receive future updates. name: cc - description: Sends a carbon-copy of this update to a comma-delimited list of administrative email addresses. These people will receive future updates. name: admin-cc - description: Ticker owner. name: owner - description: Ticket status. name: status - description: Ticket priority, given as number in the range 0-100. name: priority - description: The ticket content. name: text - description: Ticket initial priority, given as number in the range 0-100. name: initial-priority - description: Ticket final priority, given as number in the range 0-100. name: final-priority - description: Ticket MemberOF ID. isArray: true name: member-of - description: Ticket Members ID. isArray: true name: members - description: Ticket DependedOn ID. isArray: true name: depends-on - description: Ticket DependedOnBy ID. isArray: true name: depended-on-by - description: Ticket RefersTo ID. isArray: true name: refers-to - description: Ticket ReferredToBy ID. isArray: true name: referred-to-by - description: Attachment to add to the ticket, given as Entry ID. Comma-separated values supported, e.g., entryID1,entryID2. isArray: true name: attachment - description: 'Ticket custom fields, given in format: field1=value1,field2=value2, e.g. IP=8.8.8.8,HowReported=Email. Note: the command does not create custom fields, these should be created on RTIR.' name: customfields description: Create new ticket on RTIR. name: rtir-create-ticket outputs: - contextPath: RTIR.Ticket.ID description: Ticket ID. type: number - contextPath: RTIR.Ticket.InitialPriority description: Ticket priority (0-100). type: number - contextPath: RTIR.Ticket.Priority description: Ticket priority (0-100). type: number - contextPath: RTIR.Ticket.FinalPriority description: Ticket final priority (0-100). type: number - contextPath: RTIR.Ticket.Owner description: Ticket owner. type: string - contextPath: RTIR.Ticket.Subject description: Ticket subject. type: string - contextPath: RTIR.Ticket.Creator description: Ticker creator. type: string - arguments: - description: 'Ticket ID.' name: ticket-id - description: Ticket subject. name: subject - description: Ticket queue (Comma-separated values supported, e.g., General,Incident reports,Incidents). name: queue required: true - description: 'Ticket status.' name: status - description: Ticket creator. name: creator - description: Ticket priority (number in range 0-100). name: priority-equal-to - description: Ticket priority (number in range 0-100). name: priority-greater-than - description: Date after which the ticket was created, in format of YYYY-MM-DD, e.g. 2011-02-24. name: created-after - description: Date on which the ticket was created, in format of YYYY-MM-DD, e.g. 2011-02-24. name: created-on - description: Date before which the ticket was created, in format of YYYY-MM-DD, e.g. 2011-02-24. name: created-before - description: Ticker owner. name: owner - description: Ticket due date, in format of YYYY-MM-DD, e.g. 2011-02-24. name: due - defaultValue: '0' description: A limit for the max number of results that will return from the search. 0 means no limit, which is the default. name: results_limit description: Search for tickets on RTIR. name: rtir-search-ticket outputs: - contextPath: RTIR.Ticket.ID description: Ticket ID. type: number - contextPath: RTIR.Ticket.State description: Ticket state. type: string - contextPath: RTIR.Ticket.Creator description: Ticket creator. type: string - contextPath: RTIR.Ticket.Subject description: Ticket subject. type: string - contextPath: RTIR.Ticket.Created description: Ticket creation date. type: date - contextPath: RTIR.Ticket.Priority description: Ticket priority (0-100). type: number - contextPath: RTIR.Ticket.InitialPriority description: Ticket initial priority (0-100). type: number - contextPath: RTIR.Ticket.FinalPriority description: Ticket final priority (0-100). type: number - contextPath: RTIR.Ticket.Queue description: Ticket queue. type: string - contextPath: RTIR.Ticket.Owner description: Ticket owner. type: string - contextPath: RTIR.Ticket.IP description: Ticket custom field - IP address. type: string - contextPath: RTIR.Ticket.HowReported description: Ticket custom field - How ticket was reported. type: string - contextPath: RTIR.Ticket.Customer description: Ticket custom field - Customer. type: string - arguments: - description: Ticket ID to close. name: ticket-id required: true description: Sets a ticket as resolved on RTIR. name: rtir-resolve-ticket outputs: - contextPath: RTIR.Ticket.ID description: Ticket ID. type: number - contextPath: RTIR.Ticket.State description: Ticket state. type: string - arguments: - description: Ticket ID. name: ticket-id required: true - description: Ticket subject. name: subject - description: Ticket priority, number in range 0-100. name: priority - description: Ticket final priority, number in range 0-100. name: final-priority - description: Ticket owner. name: owner - description: Ticket status. name: status - description: Ticket due date, in format of YYYY-MM-DD, e.g. 2011-02-24. name: due - description: Ticket MemberOF ID. isArray: true name: member-of - description: Ticket Members ID. isArray: true name: members - description: Ticket DependedOn ID. isArray: true name: depends-on - description: Ticket DependedOnBy ID. isArray: true name: depended-on-by - description: Ticket RefersTo ID. isArray: true name: refers-to - description: Ticket ReferredToBy ID. isArray: true name: referred-to-by - description: 'Ticket custom fields, given in format: field1=value1,field2=value2, e.g. IP=8.8.8.8,HowReported=Email. Note: the command does not create custom fields, these should be created on RTIR.' name: customfields description: Modify a ticket on RTIR. name: rtir-edit-ticket outputs: - contextPath: RTIR.Ticket.ID description: Ticket ID. type: number - contextPath: RTIR.Ticket.FinalPriority description: Ticket final priority (0-100). type: number - contextPath: RTIR.Ticket.Priority description: Ticket priority (0-100). type: number - contextPath: RTIR.Ticket.Owner description: Ticket owner. type: string - contextPath: RTIR.Ticket.State description: Ticket state. type: string - contextPath: RTIR.Ticket.Subject description: Ticket subject. type: string - arguments: - description: Ticket ID to get history of. name: ticket-id required: true description: Gets a list of all the history items for a given ticket. name: rtir-ticket-history outputs: - contextPath: RTIR.Ticket.ID description: Ticket ID. type: number - contextPath: RTIR.Ticket.History.Content description: Ticket history content. type: string - contextPath: RTIR.Ticket.History.Created description: Ticket history creation date. type: date - contextPath: RTIR.Ticket.History.Creator description: Ticket history creator. type: string - contextPath: RTIR.Ticket.History.Description description: Ticket history description. type: string - contextPath: RTIR.Ticket.History.NewValue description: Value updated in history transaction. type: string - arguments: - description: Ticket ID to get. name: ticket-id required: true description: Gets the data for a single ticket. name: rtir-get-ticket outputs: - contextPath: RTIR.Ticket.LinkedTo.ID description: Linked ticket ID. type: number - contextPath: RTIR.Ticket.ID description: Ticket ID. type: number - contextPath: RTIR.Ticket.State description: Ticket state. type: string - contextPath: RTIR.Ticket.Creator description: Ticket creator. type: string - contextPath: RTIR.Ticket.Subject description: Ticket subject. type: string - contextPath: RTIR.Ticket.Created description: Ticket creation date. type: date - contextPath: RTIR.Ticket.Priority description: Ticket priority (0-100). type: number - contextPath: RTIR.Ticket.InitialPriority description: Ticket initial priority (0-100). type: number - contextPath: RTIR.Ticket.FinalPriority description: Ticket final priority (0-100). type: number - contextPath: RTIR.Ticket.Queue description: Ticket queue. type: string - contextPath: RTIR.Ticket.Owner description: Ticket owner. type: string - contextPath: RTIR.Ticket.IP description: Ticket custom field - IP address. type: string - contextPath: RTIR.Ticket.HowReported description: Ticket custom field - How ticket was reported. type: string - contextPath: RTIR.Ticket.Customer description: Ticket custom field - Customer. type: string - arguments: - description: Ticket ID to get attachments of. name: ticket-id required: true description: Gets a list of all attachments details and data content related to the ticket. name: rtir-ticket-attachments outputs: - contextPath: RTIR.Ticket.ID description: Ticket ID. type: number - contextPath: RTIR.Ticket.Attachment.ID description: Attachment ID. type: number - contextPath: RTIR.Ticket.Attachment.Name description: Attachment file name. type: string - contextPath: RTIR.Ticket.Attachment.Size description: Attachment file size. type: string - contextPath: RTIR.Ticket.Attachment.Type description: Attachment file type. type: string - contextPath: File.EntryID description: Demisto entry ID of attachment. type: string - contextPath: File.Size description: File size. type: number - contextPath: File.SHA1 description: File SHA1. type: string - contextPath: File.SHA256 description: File SHA256. type: string - contextPath: File.Name description: File name. type: string - contextPath: File.SSDeep description: File SSDeep. type: string - contextPath: File.Info description: File type information. type: string - contextPath: File.Type description: File type. type: string - contextPath: File.MD5 description: File MD5. type: string - contextPath: File.Extension description: File extension. type: string - arguments: - description: Ticket ID to add comment to. name: ticket-id required: true - description: Comment text. name: text required: true - description: Attachment to add to the ticket, given as Entry ID. Comma-separated values supported, e.g., entryID1,entryID2. isArray: true name: attachment description: Add a comment to an existing ticket. name: rtir-add-comment - arguments: - description: Ticket ID to send the reply to the user. name: ticket-id required: true - description: reply text. name: text required: true - description: Email of the user to send the reply. isArray: true name: cc description: Send a reply from an existing ticket to the user. name: rtir-add-reply isfetch: true script: '-' type: python subtype: python3 dockerimage: demisto/python3:3.12.13.10116658 tests: - RTIR Test fromversion: 5.0.0