Jira Server (On-Premise)

Create issues in JIRA with the incidents from Squadcast and vice versa and also sync the status bidirectionally.

You can use this integration guide to install and configure the Squadcast extension in JIRA Server (On-Premise) in order to automatically create issues in JIRA projects from Squadcast and vice versa. The status of the issues on JIRA and incidents in Squadcast will automatically be in sync.


  1. A valid Squadcast cloud / On-Premise subscription on Pro Plan

  2. You should have JIRA Server (On-Premise) version installed on your machine with a publicly accessible URL

  3. A user account in JIRA Server with Administrator privileges

  4. Base URL must be set in JIRA settings and it must be publicly accessible as mentioned above

  5. Install the Squadcast Plugin from the Atlassian App Store

Integration Steps

  1. Move over to the Integrations from the sidebar and choose to Integrate with JIRA Server.
  1. Now click on Configure to receive a token
  1. Copy the displayed token.

  2. Go to Manage Apps page on your JIRA Server Account from the Settings dropdown.

  1. Select the Squadcast Plugin from the User-installed apps. Click Configure.
  1. In the configuration page, paste the Squadcast token in the JIRA Integration Key text box. Then click Integrate.
  1. Move over to Squadcast and click on Test Connection. You will then receive a success message right below the text box. Post this, click on Next
  1. Select the Jira project in which issue needs to be created and select the issue type and click Next.
  1. Then map the Jira issue status to the available Squadcast statuses and click Next.
  1. Then select the mode in which you want to add an incident to Jira: Manually or Automatically.
    Now, there are 2 sections:
    • Add Services to Jira
    • JQL - Service Mapping

Add Services to Jira: If an incident is created for any service selected in this section, a corresponding Jira ticket would be created in the configured project having the configured issueType.

JQL - Service Mapping: If a ticket is created in Jira, then the mappings defined in this section would be iterated one-by-one and incident would be created for the service corresponding to the first JQL that evaluated to be true for that Jira ticket. If none of the JQL matched, then no incident would be created in Squadcast.


The issue must be in the same Jira project and be the same Jira Issue type. If you are using Jira Service Desk, incidents are created from JQL before automation rules are applied.

So, to summarize,

Add Services to Jira: Handles Jira ticket creation corresponding to incident creation in Squadcast.
JQL - Service Mapping: Handles Squadcast incident creation corresponding to ticket creation in Jira.

That's it! Your JIRA Server Integration is good to go.

The statuses of the Squadcast Incident and JIRA Issue will be automatically synced as per the mapping configured.


If the Squadcast incident reaches either Resolved or Suppressed status, the bidirectional status syncing will stop even if the issue is re-opened in JIRA, as these both are end states in Squadcast.

Usage of the Automatic and Manual Modes

Automatic mode

If you have chosen the Automatic mode while configuring Jira Server then you need not do anything. Any incident triggered for the selected service will automatically create an issue in the selected Jira project with the configured issue type.

Manual mode

If the chosen mode is Manual, follow the below steps to create a issue in Jira.

  1. Open the incident in Squadcast and click on More Actions button.
  1. Select Jira Server action and click on Create a issue in Jira button.

An issue will be created in the selected Jira project with the configured issue type and this action will be recorded in the incident timeline with a hyperlink to the created Jira issue.

Updated 13 days ago

Jira Server (On-Premise)

Create issues in JIRA with the incidents from Squadcast and vice versa and also sync the status bidirectionally.

Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.