For the complete documentation index, see llms.txt. This page is also available as Markdown.

Ticketing systems overview

Overview of the ticketing system connectors Harness supports and where to set up each one.

Harness ticketing system connectors integrate your issue-tracking tools with Harness. A connector provides the connection information and credentials Harness needs to create, update, and track issues from your pipelines, and to gate approvals on the status of those issues.

Use a ticketing system connector when you want a pipeline to open an issue for a deployment, update an existing issue with deployment status, or wait for an issue to reach a specific state before a stage proceeds.


Before you begin

  • You can create a ticketing system connector at the Project, Organization, or Account scope.

  • You need permission to create and edit connectors. For details, go to Configure RBAC.

  • If Harness connects to your ticketing system through a Harness Delegate, install and register a delegate before you configure the connector. For details, go to Delegate overview.


Ticketing system connectors

Harness supports the following ticketing system connectors.

  • Jira connector: Connect Harness to Jira to create and update Jira issues, and to use Jira issues in Approval steps.

  • JSM connector: Connect Harness to Jira Service Management (JSM) to create and update JSM tickets, and to use JSM tickets in Approval steps.

  • ServiceNow connector: Connect Harness to ServiceNow to create and update ServiceNow tickets, and to use ServiceNow tickets in Approval steps.


How Harness uses ticketing system connectors

Pipelines use a ticketing system connector in two ways:

  • CD steps: A Jira Create, Jira Update, JSM Create, JSM Update, ServiceNow Create, or ServiceNow Update step uses the connector to open or modify a ticket as part of a stage, so the ticket reflects what the pipeline is doing.

  • Approval steps: A Jira Approval, JSM Approval, or ServiceNow Approval step uses the connector to poll an existing ticket and hold the stage until the ticket reaches an approved status, so a pipeline cannot proceed without sign-off tracked in your ticketing system.


Next steps

Last updated

Was this helpful?