Fortinet black logo

Request Tracker

Home FortiSOAR Connectors Request Tracker
2.1.0
2.1.0
2.0.0
1.1.0
1.0.0

Request Tracker v2.1.0

About the connector

Request Tracker is an open source issue tracking and workflow platform used to coordinate tasks and manage requests among a community of users.

This document provides information about the Request Tracker connector, which facilitates automated interactions with Request Tracker using FortiSOAR™ playbooks. Add the Request Tracker connector as a step in FortiSOAR™ playbooks and perform automated ticket management on Request tracker by implementing operations, such as creating and updating a ticket on Request Tracker and retrieving the history of a ticket from Request Tracker.

Version information

Connector Version: 2.1.0

FortiSOAR™ Version Tested on: 4.12.1-253

Authored By: Fortinet

Certified: Yes

Release Notes for version 2.1.0

Following enhancements have been made to the Request Tracker Connector in version 2.1.0:

  • Added the following new operations and playbooks:

    • Get Transaction Attachments

    • Get Transaction Details

    • Get Attachment Details

  • Added the Get Transactions and Create Attachment input parameters to the Get Ticket Properties operation.

Installing the connector

All connectors provided by FortiSOAR™ are delivered using a FortiSOAR™ repository. Therefore, you must set up your FortiSOAR™ repository and use the yum command to install connectors:

yum install cyops-connector-request-tracker

For the detailed procedure to install a connector, click here.

Prerequisites to configuring the connector

  • You must have the URL of Request Tracker server to which you will connect and perform automated operations and credentials (either the API token or a username-password pair) to access that server.
  • To access the FortiSOAR™ UI, ensure that port 443 is open through the firewall for the CyOPsTM instance.

Configuring the connector

For the procedure to configure a connector, click here.

Configuration parameters

In FortiSOAR™, on the Connectors page, click the Request Tracker connector row, and in the Configure tab enter the required configuration details.

Parameter Description
Server URL URL of the Request Tracker server to which you will connect and perform automated operations.
Authentication Type of authentication used to connect to the Request Tracker server to which you will connect and perform automated operations. You can choose either Token or Username/Password.
Token If you choose the authentication type as Token, then specify the API token that is configured for your account to access the Request Tracker server to which you will connect and perform the automated operations.
Username If you choose the authentication type as Username/Password, then specify the username that is used to access the Request Tracker server to which you will connect and perform the automated operations.
Password If you choose the authentication type as Username/Password, then specify the password that is used to access the Request Tracker server to which you will connect and perform the automated operations.
Verify SSL Specifies whether the SSL certificate for the server is to be verified or not.
By default, this option is set as True.

Actions supported by the connector

The following automated operations can be included in playbooks, and you can also use the annotations to access operations from FortiSOAR™ release 4.10.0 onwards:

Function Description Annotation and Category
Create Ticket Creates a ticket in Request Tracker based on input parameters you have specified. create_ticket
Investigation
Get Ticket Properties Retrieves the properties of an existing ticket from Request Tracker based on ticket ID and other input parameters you have specified. get_ticket_properties
Investigation
Get Ticket/Queue History Retrieves the history details of an existing ticket or queue from Request Tracker based on ticket or queue ID and other input parameters you have specified. get_record_history
Investigation
Search Ticket Searches for a ticket in Request Tracker based on the query and other input parameters you have specified. search_record
Investigation
Comment Ticket Adds a comment to an existing ticket on Request Tracker based on ticket ID you have specified. comment_ticket
Investigation
Update Ticket Updates an existing ticket on Request Tracker based on input parameters you have specified. update_ticket
Investigation
Delete Ticket Deletes an existing ticket from Request Tracker based on ticket ID you have specified. delete_ticket
Investigation
Create Queue Creates a queue in Request Tracker based on input parameters you have specified. create_queue
Investigation
List Queue Retrieves all queues from Request Tracker. list_queue
Investigation
Get Queue Properties Retrieves the properties of an existing queue from Request Tracker based on queue ID you have specified. get_queue_properties
Investigation
Update Queue Updates an existing queue on Request Tracker based on input parameters you have specified. update_queue
Containment
Delete Queue Deletes an existing queue from Request Tracker based on input parameters you have specified. delete_queue
Investigation
Get Transaction Attachments Retrieves all attachments for a specified transaction from Request Tracker based on the transaction ID and other input parameters you have specified. get_transaction_attachments
Investigation
Get Transaction Details Retrieves the details for a specified transaction from Request Tracker based on the transaction ID you have specified. get_transaction_details
Investigation
Get Attachment Details Retrieves the details for a specified attachment from Request Tracker based on the attachment ID you have specified. get_attachment_details
Investigation

operation: Create Ticket

Input parameters

Parameter Description
Queue ID ID of the queue in Request Tracker in which you want to create a new ticket.
Subject Subject of the ticket that you want to create in Request Tracker.
From Email ID of the user from whose ID you want to create a ticket in Request Tracker.
For example, user1@example.com
To Email ID of the user on whose ID you want to send the ticket that you are creating on Request Tracker.
For example, rt@example.com
Content Content or brief description of the ticket that you want to create in Request Tracker.
Custom Fields (Optional) You can add custom fields, in the JSON format, in the ticket that you want to create in Request Tracker.
For example, {"Severity": "Low"}

Output

The output contains the following populated JSON schema:
{
"type": "",
"id": "",
"_url": ""
}

operation: Get Ticket Properties

Input parameters

Parameter Description
Ticket ID ID of the ticket whose properties you want to retrieve from Request Tracker.
Get Transactions (Optional) Select this option to retrieve all transactions details for the ticket you have specified.
Create Attachment (Optional) Select this option to create attachments in FortiSOAR™ for the ticket you have specified.

Output

The output contains the following populated JSON schema:
{
"LastUpdated": "",
"Resolved": "",
"FinalPriority": "",
"CustomFields": {},
"TimeWorked": "",
"Type": "",
"RT::CustomRole-1": [],
"Subject": "",
"id": "",
"TimeEstimated": "",
"Due": "",
"Created": "",
"Priority": "",
"InitialPriority": "",
"_hyperlinks": [
{
"ref": "",
"_url": "",
"id": ""
}
],
"EffectiveId": {
"type": "",
"_url": "",
"id": ""
},
"Requestor": [],
"LastUpdatedBy": {
"type": "",
"_url": "",
"id": ""
},
"Started": "",
"Owner": {
"type": "",
"_url": "",
"id": ""
},
"TimeLeft": "",
"Attachment": {
"cyops_attachment_ids": [],
"rt_attachment_meta": [{"filename": "", "attachment_id": ""}]
},
"AdminCc": [],
"RT::CustomRole-2": [],
"Cc": [],
"Status": "",
"Queue": {
"type": "",
"_url": "",
"id": ""
},
"Starts": "",
"Creator": {
"type": "",
"_url": "",
"id": ""
},
"Transaction": [
{
"Creator": {
"type": "",
"_url": "",
"id": ""
},
"_hyperlinks": [
{
"ref": "self",
"_url": ""
},
{
"ref": "",
"_url": ""
}
],
"id": "",
"Created": "",
"Object": {
"type": "",
"_url": "",
"id": ""
},
"TimeTaken": "",
"Type": ""
}
]
}

operation: Get Ticket/Queue History

Input parameters

Parameter Description
Ticket/Queue Select the record type, either ticket or queue, for which you want to retrieve the history details from Request Tracker.
ID ID of the ticket or queue whose history you want to retrieve from Request Tracker.
Page Size (Optional) Number of result records that you want to display on one page.
By default, it is set as 20 records. However, you can increase it to 100.
Page Number (Optional) Page number from which you want to retrieve records.
By default, it is set to 1.

Output

The output contains the following populated JSON schema:
{

"count": "",
"page": "",
"per_page": "",
"items": [
{
"type": "",
"id": "",
"_url": ""
}
],
"total": ""
}

operation: Search Ticket

Input parameters

Parameter Description
Query Query based on which you want to search for tickets in Request Tracker.
For example, If you want to find all tickets that have no owner and whose status is new or open, you can add the following query: Owner = 'Nobody' AND ( Status = 'new' OR Status = 'open' )
Page Size (Optional) Number of result records that you want to display on one page.
By default, it is set as 20 records. However, you can increase it to 100.
Page Number (Optional) Page number from which you want to retrieve records.
By default, it is set to 1.

Output

The output contains the following populated JSON schema:
{

"count": "",
"page": "",
"per_page": "",
"items": [
{
"type": "",
"id": "",
"_url": ""
}
],
"total": ""
}

operation: Update Ticket

Input parameters

Parameter Description
Ticket ID ID of the ticket that you want to update in Request Tracker.
Content Content of brief description of the ticket that you want to update in Request Tracker.
Subject (Optional) Subject of the ticket that you want to update in Request Tracker.
From (Optional) Email ID of the user from whose ID you want to update the ticket in Request Tracker.
For example, user1@example.com
To (Optional) Email ID of the user on whose ID you want to send the ticket that you are updating on Request Tracker.
For example, rt@example.com
Custom Fields (Optional) You can add custom fields, in the JSON format, in the ticket that you want to update in Request Tracker.
For example, {"Severity": "Low"}

Output

No output schema is available at this time.

operation: Comment Ticket

Input parameters

Parameter Description
Ticket ID ID of the ticket in Request Tracker to which you want to add a comment.
Comment Text Content of the comment that you want to add to an existing ticket in Request Tracker.

Output

The output contains a non-dictionary value.

operation: Delete Ticket

Input parameters

Parameter Description
Ticket ID ID of the ticket that you want to delete from Request Tracker.

Output

The output contains a non-dictionary value.

operation: Create Queue

Input parameters

Parameter Description
Name Name of the queue that you want to create in Request Tracker.
Subject Tag Subject of the queue that you want to create in Request Tracker.
Description Content or brief description of the queue that you want to create in Request Tracker.
Custom Fields (Optional) You can add custom fields, in the JSON format, in the queue that you want to create in Request Tracker. For example, {"Severity": "Low"}.

Output

The output contains the following populated JSON schema:
{
"type": "",
"id": "",
"_url": ""
}

operation: List Queue

Input parameters

Parameter Description
Page Size (Optional) Number of result records that you want to display on one page.
By default, it is set as 20 records. However, you can increase it to 100.
Page Number (Optional) Page number from which you want to retrieve records.
By default, it is set to 1.

Output

The output contains the following populated JSON schema:
{
"count": "",

"per_page": "",
"page": "",
"total": "",
"items": [
{
"type": "",
"id": "",
"_url": ""
}
]
}

operation: Get Queue Properties

Input parameters

Parameter Description
Queue ID ID of the queue whose properties you want to retrieve from Request Tracker.

Output

The output contains the following populated JSON schema:
{
"LastUpdated": "",
"SubjectTag": "",
"_hyperlinks": [
{
"ref": "",
"_url": ""
}
],
"id": "",
"Name": "",
"Creator": {
"type": "",
"id": "",
"_url": ""
},
"Disabled": "",
"CustomFields": {},
"SLADisabled": "",
"Lifecycle": "",
"RT::CustomRole-1": "",
"LastUpdatedBy": {
"type": "",
"id": "",
"_url": ""
},
"AdminCc": [],
"SortOrder": "",
"RT::CustomRole-2": "",
"Cc": [],
"Description": "",
"Created": ""
}

operation: Update Queue

Input parameters

Parameter Description
Queue ID ID of the queue that you want to update in Request Tracker.
Subject Tag Subject of the queue that you want to update in Request Tracker.
Description (Optional) Content or brief description of the queue that you want to update in Request Tracker.
Custom Fields (Optional) You can add custom fields, in the JSON format, in the queue that you want to update in Request Tracker. For example, {"Severity": "Low"}.

Output

The output contains the following populated JSON schema:
{
"type": "",
"id": "",
"_url": ""
}

operation: Delete Queue

Input parameters

Parameter Description
Queue ID ID of the queue that you want to delete from Request Tracker.

Output

The output contains a non-dictionary value.

operation: Get Transaction Attachments

Input parameters

Parameter Description
Transaction ID ID of the transaction whose attachments you want to retrieve from Request Tracker.
Page Size (Optional) Number of result records that you want to display on one page.
By default, it is set as 20 records. However, you can increase it to 100.
Page Number (Optional) Page number from which you want to retrieve records.
By default, it is set to 1.

Output

The output contains the following populated JSON schema:
{
"count": "",
"page": "",
"per_page": "",
"items": [
{
"type": "",
"id": "",
"_url": ""
}
],
"total": ""
}

operation: Get Transaction Details

Input parameters

Parameter Description
Transaction ID ID of the transaction whose details you want to retrieve from Request Tracker.

Output

The output contains the following populated JSON schema:
{
"Creator": {
"type": "",
"id": "",
"_url": ""
},
"_hyperlinks": [
{
"ref": "",
"_url": ""
}
],
"id": "",
"Created": "",
"Object": {
"type": "",
"id": "",
"_url": ""
},
"TimeTaken": "",
"Type": ""
}

operation: Get Attachment Details

Input parameters

Parameter Description
Ticket ID ID of the ticket whose attachment details you want to retrieve from Request Tracker.
Attachment ID ID of the attachment whose details you want to retrieve from Request Tracker.
Create Attachment (Optional) Select this option to create the attachment in FortiSOAR™ for the attachment ID that you have specified.

Output

The output contains the following populated JSON schema:
{
"cyops_attachment_ids": [],
"rt_attachment_meta": []
}

Included playbooks

The Sample - Request Tracker - 2.1.0 playbook collection comes bundled with the Request Tracker connector. This playbook contains steps using which you can perform all supported actions. You can see the bundled playbooks in the Automation > Playbooks section in FortiSOAR™ after importing the Request Tracker connector.

  • Comment Ticket
  • Create Queue
  • Create Ticket
  • Delete Queue
  • Delete Ticket
  • Get Attachment Details
  • Get Transaction Attachments
  • Get Transaction Details
  • Get Queue Properties
  • Get Ticket Properties
  • Get Ticket/Queue History
  • List Queue
  • Search Ticket
  • Update Queue
  • Update Ticket

Note: If you are planning to use any of the sample playbooks in your environment, ensure that you clone those playbooks and move them to a different collection since the sample playbook collection gets deleted during connector upgrade and delete.

Previous
Next

About the connector

Request Tracker is an open source issue tracking and workflow platform used to coordinate tasks and manage requests among a community of users.

This document provides information about the Request Tracker connector, which facilitates automated interactions with Request Tracker using FortiSOAR™ playbooks. Add the Request Tracker connector as a step in FortiSOAR™ playbooks and perform automated ticket management on Request tracker by implementing operations, such as creating and updating a ticket on Request Tracker and retrieving the history of a ticket from Request Tracker.

Version information

Connector Version: 2.1.0

FortiSOAR™ Version Tested on: 4.12.1-253

Authored By: Fortinet

Certified: Yes

Release Notes for version 2.1.0

Following enhancements have been made to the Request Tracker Connector in version 2.1.0:

Installing the connector

All connectors provided by FortiSOAR™ are delivered using a FortiSOAR™ repository. Therefore, you must set up your FortiSOAR™ repository and use the yum command to install connectors:

yum install cyops-connector-request-tracker

For the detailed procedure to install a connector, click here.

Prerequisites to configuring the connector

Configuring the connector

For the procedure to configure a connector, click here.

Configuration parameters

In FortiSOAR™, on the Connectors page, click the Request Tracker connector row, and in the Configure tab enter the required configuration details.

Parameter Description
Server URL URL of the Request Tracker server to which you will connect and perform automated operations.
Authentication Type of authentication used to connect to the Request Tracker server to which you will connect and perform automated operations. You can choose either Token or Username/Password.
Token If you choose the authentication type as Token, then specify the API token that is configured for your account to access the Request Tracker server to which you will connect and perform the automated operations.
Username If you choose the authentication type as Username/Password, then specify the username that is used to access the Request Tracker server to which you will connect and perform the automated operations.
Password If you choose the authentication type as Username/Password, then specify the password that is used to access the Request Tracker server to which you will connect and perform the automated operations.
Verify SSL Specifies whether the SSL certificate for the server is to be verified or not.
By default, this option is set as True.

Actions supported by the connector

The following automated operations can be included in playbooks, and you can also use the annotations to access operations from FortiSOAR™ release 4.10.0 onwards:

Function Description Annotation and Category
Create Ticket Creates a ticket in Request Tracker based on input parameters you have specified. create_ticket
Investigation
Get Ticket Properties Retrieves the properties of an existing ticket from Request Tracker based on ticket ID and other input parameters you have specified. get_ticket_properties
Investigation
Get Ticket/Queue History Retrieves the history details of an existing ticket or queue from Request Tracker based on ticket or queue ID and other input parameters you have specified. get_record_history
Investigation
Search Ticket Searches for a ticket in Request Tracker based on the query and other input parameters you have specified. search_record
Investigation
Comment Ticket Adds a comment to an existing ticket on Request Tracker based on ticket ID you have specified. comment_ticket
Investigation
Update Ticket Updates an existing ticket on Request Tracker based on input parameters you have specified. update_ticket
Investigation
Delete Ticket Deletes an existing ticket from Request Tracker based on ticket ID you have specified. delete_ticket
Investigation
Create Queue Creates a queue in Request Tracker based on input parameters you have specified. create_queue
Investigation
List Queue Retrieves all queues from Request Tracker. list_queue
Investigation
Get Queue Properties Retrieves the properties of an existing queue from Request Tracker based on queue ID you have specified. get_queue_properties
Investigation
Update Queue Updates an existing queue on Request Tracker based on input parameters you have specified. update_queue
Containment
Delete Queue Deletes an existing queue from Request Tracker based on input parameters you have specified. delete_queue
Investigation
Get Transaction Attachments Retrieves all attachments for a specified transaction from Request Tracker based on the transaction ID and other input parameters you have specified. get_transaction_attachments
Investigation
Get Transaction Details Retrieves the details for a specified transaction from Request Tracker based on the transaction ID you have specified. get_transaction_details
Investigation
Get Attachment Details Retrieves the details for a specified attachment from Request Tracker based on the attachment ID you have specified. get_attachment_details
Investigation

operation: Create Ticket

Input parameters

Parameter Description
Queue ID ID of the queue in Request Tracker in which you want to create a new ticket.
Subject Subject of the ticket that you want to create in Request Tracker.
From Email ID of the user from whose ID you want to create a ticket in Request Tracker.
For example, user1@example.com
To Email ID of the user on whose ID you want to send the ticket that you are creating on Request Tracker.
For example, rt@example.com
Content Content or brief description of the ticket that you want to create in Request Tracker.
Custom Fields (Optional) You can add custom fields, in the JSON format, in the ticket that you want to create in Request Tracker.
For example, {"Severity": "Low"}

Output

The output contains the following populated JSON schema:
{
"type": "",
"id": "",
"_url": ""
}

operation: Get Ticket Properties

Input parameters

Parameter Description
Ticket ID ID of the ticket whose properties you want to retrieve from Request Tracker.
Get Transactions (Optional) Select this option to retrieve all transactions details for the ticket you have specified.
Create Attachment (Optional) Select this option to create attachments in FortiSOAR™ for the ticket you have specified.

Output

The output contains the following populated JSON schema:
{
"LastUpdated": "",
"Resolved": "",
"FinalPriority": "",
"CustomFields": {},
"TimeWorked": "",
"Type": "",
"RT::CustomRole-1": [],
"Subject": "",
"id": "",
"TimeEstimated": "",
"Due": "",
"Created": "",
"Priority": "",
"InitialPriority": "",
"_hyperlinks": [
{
"ref": "",
"_url": "",
"id": ""
}
],
"EffectiveId": {
"type": "",
"_url": "",
"id": ""
},
"Requestor": [],
"LastUpdatedBy": {
"type": "",
"_url": "",
"id": ""
},
"Started": "",
"Owner": {
"type": "",
"_url": "",
"id": ""
},
"TimeLeft": "",
"Attachment": {
"cyops_attachment_ids": [],
"rt_attachment_meta": [{"filename": "", "attachment_id": ""}]
},
"AdminCc": [],
"RT::CustomRole-2": [],
"Cc": [],
"Status": "",
"Queue": {
"type": "",
"_url": "",
"id": ""
},
"Starts": "",
"Creator": {
"type": "",
"_url": "",
"id": ""
},
"Transaction": [
{
"Creator": {
"type": "",
"_url": "",
"id": ""
},
"_hyperlinks": [
{
"ref": "self",
"_url": ""
},
{
"ref": "",
"_url": ""
}
],
"id": "",
"Created": "",
"Object": {
"type": "",
"_url": "",
"id": ""
},
"TimeTaken": "",
"Type": ""
}
]
}

operation: Get Ticket/Queue History

Input parameters

Parameter Description
Ticket/Queue Select the record type, either ticket or queue, for which you want to retrieve the history details from Request Tracker.
ID ID of the ticket or queue whose history you want to retrieve from Request Tracker.
Page Size (Optional) Number of result records that you want to display on one page.
By default, it is set as 20 records. However, you can increase it to 100.
Page Number (Optional) Page number from which you want to retrieve records.
By default, it is set to 1.

Output

The output contains the following populated JSON schema:
{

"count": "",
"page": "",
"per_page": "",
"items": [
{
"type": "",
"id": "",
"_url": ""
}
],
"total": ""
}

operation: Search Ticket

Input parameters

Parameter Description
Query Query based on which you want to search for tickets in Request Tracker.
For example, If you want to find all tickets that have no owner and whose status is new or open, you can add the following query: Owner = 'Nobody' AND ( Status = 'new' OR Status = 'open' )
Page Size (Optional) Number of result records that you want to display on one page.
By default, it is set as 20 records. However, you can increase it to 100.
Page Number (Optional) Page number from which you want to retrieve records.
By default, it is set to 1.

Output

The output contains the following populated JSON schema:
{

"count": "",
"page": "",
"per_page": "",
"items": [
{
"type": "",
"id": "",
"_url": ""
}
],
"total": ""
}

operation: Update Ticket

Input parameters

Parameter Description
Ticket ID ID of the ticket that you want to update in Request Tracker.
Content Content of brief description of the ticket that you want to update in Request Tracker.
Subject (Optional) Subject of the ticket that you want to update in Request Tracker.
From (Optional) Email ID of the user from whose ID you want to update the ticket in Request Tracker.
For example, user1@example.com
To (Optional) Email ID of the user on whose ID you want to send the ticket that you are updating on Request Tracker.
For example, rt@example.com
Custom Fields (Optional) You can add custom fields, in the JSON format, in the ticket that you want to update in Request Tracker.
For example, {"Severity": "Low"}

Output

No output schema is available at this time.

operation: Comment Ticket

Input parameters

Parameter Description
Ticket ID ID of the ticket in Request Tracker to which you want to add a comment.
Comment Text Content of the comment that you want to add to an existing ticket in Request Tracker.

Output

The output contains a non-dictionary value.

operation: Delete Ticket

Input parameters

Parameter Description
Ticket ID ID of the ticket that you want to delete from Request Tracker.

Output

The output contains a non-dictionary value.

operation: Create Queue

Input parameters

Parameter Description
Name Name of the queue that you want to create in Request Tracker.
Subject Tag Subject of the queue that you want to create in Request Tracker.
Description Content or brief description of the queue that you want to create in Request Tracker.
Custom Fields (Optional) You can add custom fields, in the JSON format, in the queue that you want to create in Request Tracker. For example, {"Severity": "Low"}.

Output

The output contains the following populated JSON schema:
{
"type": "",
"id": "",
"_url": ""
}

operation: List Queue

Input parameters

Parameter Description
Page Size (Optional) Number of result records that you want to display on one page.
By default, it is set as 20 records. However, you can increase it to 100.
Page Number (Optional) Page number from which you want to retrieve records.
By default, it is set to 1.

Output

The output contains the following populated JSON schema:
{
"count": "",

"per_page": "",
"page": "",
"total": "",
"items": [
{
"type": "",
"id": "",
"_url": ""
}
]
}

operation: Get Queue Properties

Input parameters

Parameter Description
Queue ID ID of the queue whose properties you want to retrieve from Request Tracker.

Output

The output contains the following populated JSON schema:
{
"LastUpdated": "",
"SubjectTag": "",
"_hyperlinks": [
{
"ref": "",
"_url": ""
}
],
"id": "",
"Name": "",
"Creator": {
"type": "",
"id": "",
"_url": ""
},
"Disabled": "",
"CustomFields": {},
"SLADisabled": "",
"Lifecycle": "",
"RT::CustomRole-1": "",
"LastUpdatedBy": {
"type": "",
"id": "",
"_url": ""
},
"AdminCc": [],
"SortOrder": "",
"RT::CustomRole-2": "",
"Cc": [],
"Description": "",
"Created": ""
}

operation: Update Queue

Input parameters

Parameter Description
Queue ID ID of the queue that you want to update in Request Tracker.
Subject Tag Subject of the queue that you want to update in Request Tracker.
Description (Optional) Content or brief description of the queue that you want to update in Request Tracker.
Custom Fields (Optional) You can add custom fields, in the JSON format, in the queue that you want to update in Request Tracker. For example, {"Severity": "Low"}.

Output

The output contains the following populated JSON schema:
{
"type": "",
"id": "",
"_url": ""
}

operation: Delete Queue

Input parameters

Parameter Description
Queue ID ID of the queue that you want to delete from Request Tracker.

Output

The output contains a non-dictionary value.

operation: Get Transaction Attachments

Input parameters

Parameter Description
Transaction ID ID of the transaction whose attachments you want to retrieve from Request Tracker.
Page Size (Optional) Number of result records that you want to display on one page.
By default, it is set as 20 records. However, you can increase it to 100.
Page Number (Optional) Page number from which you want to retrieve records.
By default, it is set to 1.

Output

The output contains the following populated JSON schema:
{
"count": "",
"page": "",
"per_page": "",
"items": [
{
"type": "",
"id": "",
"_url": ""
}
],
"total": ""
}

operation: Get Transaction Details

Input parameters

Parameter Description
Transaction ID ID of the transaction whose details you want to retrieve from Request Tracker.

Output

The output contains the following populated JSON schema:
{
"Creator": {
"type": "",
"id": "",
"_url": ""
},
"_hyperlinks": [
{
"ref": "",
"_url": ""
}
],
"id": "",
"Created": "",
"Object": {
"type": "",
"id": "",
"_url": ""
},
"TimeTaken": "",
"Type": ""
}

operation: Get Attachment Details

Input parameters

Parameter Description
Ticket ID ID of the ticket whose attachment details you want to retrieve from Request Tracker.
Attachment ID ID of the attachment whose details you want to retrieve from Request Tracker.
Create Attachment (Optional) Select this option to create the attachment in FortiSOAR™ for the attachment ID that you have specified.

Output

The output contains the following populated JSON schema:
{
"cyops_attachment_ids": [],
"rt_attachment_meta": []
}

Included playbooks

The Sample - Request Tracker - 2.1.0 playbook collection comes bundled with the Request Tracker connector. This playbook contains steps using which you can perform all supported actions. You can see the bundled playbooks in the Automation > Playbooks section in FortiSOAR™ after importing the Request Tracker connector.

Note: If you are planning to use any of the sample playbooks in your environment, ensure that you clone those playbooks and move them to a different collection since the sample playbook collection gets deleted during connector upgrade and delete.

Previous
Next