Create Jira issues from your incidents, self-hosted
Spike connects to your self-hosted Jira Data Center or Server so any incident can become a tracked Jira issue — created by hand in a click or automatically with Playbooks — while the connection runs against your own instance, behind your firewall.
Enter your Jira base URL, client ID and client secret to connect
What you can do
Everything the Jira Data Center integration does
Create Jira issues from any incident
Open an issue on your self-hosted Jira straight from an incident — pick the project, issue type and summary, and the ticket lands in your own instance.
Authenticate through Application Links
Spike connects as an incoming Application Link you create inside Jira, so the OAuth credentials and the base URL stay under your control.
Automate it with Playbooks
Add a “create a Jira issue” step to a Playbook and matching incidents open a ticket in your instance on their own, with no clicks.
Incident context travels with the issue
Spike pushes the incident title and details outbound into the new ticket. The connection is one-way — Spike sends to Jira, and changes in Jira don’t sync back.
Why connect self-hosted Jira?
For teams running Jira on their own infrastructure, the follow-up to an incident belongs in a tracker that never leaves the building. Spike’s self-hosted Jira integration opens a Jira Data Center or Server issue from any incident — by hand or automatically with Playbooks — without routing your work through a hosted Atlassian tenant.
The connection is built on Jira’s own Application Links: you register Spike as an incoming external application inside your instance, and Spike authenticates with the client ID, client secret and base URL you provide. Data flows one way — Spike pushes the incident’s title and details outbound into the new issue, and changes made in Jira don’t sync back — so the integration stays simple to reason about and everything created lands in the instance you control.
Set up the Jira Data Center integration
Register Spike as an incoming Application Link in your own Jira, drop the credentials into Spike, and start opening Jira issues from any incident — no data leaves your servers on the way in.
Step 1: Create an incoming Application Link in Jira
In Jira, go to Settings → Applications → Application Links and click Create link. Choose External application and Incoming, then fill in the form — Name: Spike, Callback URL: https://app.spike.sh/task-management/jira/self-hosted/auth/callback, Permission: Write — and save. Copy the generated client ID and client secret.
Step 2: Connect JIRA server in Spike
In Spike, open Settings → Organisation, find the task-management integrations and select JIRA server. Enter your base URL (for example https://jira.mydomain.com, with no trailing slash), the client ID and the client secret, then click Connect.
Step 3: Grant permission and create an issue
Jira opens to validate the link — grant the requested permission. Once it’s connected, open any incident and create a Jira issue on your instance, choosing the project, issue type and summary.
That's it — Jira Data Center alerts now page whoever is on call.
