Spike.sh
DashboardWebsiteHUB
Spike.sh
Spike.sh
  • Introduction
  • What is Spike.sh?
  • Incidents
    • What is an incident?
    • Incident lifecycle
    • Incident statuses
    • How to change incident status?
    • Acknowledge timeout
    • Grouping incidents
    • Priority and Severity
    • Mute alerts
    • Reassign incidents
    • Sharing incidents
    • Why does message parsing fail?
    • Rate limiting on duplicate incidents
  • Alerts
    • Phone
    • SMS
    • Mobile app alerts
    • E-mail
    • Slack
    • Microsoft Teams
    • WhatsApp
    • Telegram
    • Pushover
    • Discord
    • Alert rules
    • Title Remapper
    • Personal alerts management
      • During office hours
      • Out of office
      • Resolved incident alerts
      • Deep work & Cooldown modes
  • Services
    • Introduction to services on Spike
  • Escalations
    • Introduction to escalations
    • How to create an escalation policy?
    • Repeat escalations
    • Archive escalation policy
  • Collaboration
    • Task management integrations
      • JIRA Cloud
      • JIRA server (self-hosted)
      • ClickUp
      • Linear
      • Shortcut
    • Helpdesk integrations
      • Zendesk
      • Freshdesk
      • Supportpal
    • War rooms
  • On-call schedules
    • Introduction to On-call schedules
    • Create On-call schedule
    • Introduction to Slots in schedules
    • Introduction to Layers in on-call schedules
    • Override an on-call
    • Add on-call schedule to your calendar
    • Notifications for on-call shifts
    • Change on-call rotation day
  • Playbooks
    • Introduction to Playbooks
    • Actions in Playbooks
    • Automating your Playbooks
    • Run Playbooks manually
  • Status Pages
    • Create Status page
    • Style your status page
    • Incidents on status page
    • Create Planned Maintenance on status page
    • Edit Planned Maintenance
    • Add custom domain to status page
    • Manage your subscribers
    • Embed status page notifications on your website
    • Live status widget
  • Uptime
    • Create Uptime monitor
    • Link uptime to Status Page
  • Integrations guidelines
    • Create integration and service on our dashboard
    • Setup integrations
    • Archive an integration
    • Integrating with Webhooks
    • Integrate Spike with Email
    • Integrate Spike with AWS
    • Integrate Spike with Google Cloud
    • Integrate Spike with Sematext
    • Integrate Spike with Healthchecks
    • Integrate Spike with Pingdom
    • Integrate Spike.sh with Sentry
    • Integrate Spike with Apex ping
    • Integrate Spike with Uptime Robot
    • Integrate Spike with Twilio
    • Integrate Spike with Microsoft Azure
    • Integrate Spike with Honeybadger
    • Integrate Spike with Rollbar
    • Integrate Spike with Travis CI
    • Integrate Spike with Heroku
    • Integrate Spike with Datadog
    • Integrate Spike with Axiom
    • Integrate Spike with Needle.sh
    • Integrate Spike with Cronitor
    • Integrate Spike with Bugsnag
    • Integrate Spike with Grafana
    • Integrate Spike with Prometheus
    • Integrate Spike with Instana
    • Integrate Spike with Zapier
    • Integrate Spike with Librato
    • Integrate Spike with Checkly
    • Integrate Spike with AppSignal
    • Integrate Spike with New Relic
    • Integrate Spike with Site24x7
    • Integrate Spike with Stackify
    • Integrate Spike with Scout-apm
    • Integrate Spike with Oh-Dear
    • Integrate Spike with Nixstats
    • Integrate Spike with Server Density
    • Integrate Spike with Raygun
    • Integrate Spike with Lightstep
    • Integrate Spike with Runscope
    • Integrate Spike with Honeycomb
    • Integrate Spike with Graylog
    • Integrate Spike with Checkmk
    • Integrate Spike with Hyperping
    • Integrate Spike with Epsagon
    • Integrate Spike with Uptime
    • Integrate Spike with Splunk
    • Integrate Spike with Sumo Logic
    • Integrate Spike with Thousand Eyes
    • Integrate Spike with Loggly
    • Integrate Spike with Elastic Cloud
    • Integrate Spike with App Optics
    • Integrate Spike with NodePing
    • Integrate Spike with Scalyr
    • Integrate Spike with Moogsoft
    • Integrate Spike with AppDynamics
    • Integrate Spike with Dynatrace
    • Integrate Spike with CopperEgg
    • Integrate Spike with Coralogix
    • Integrate Spike with ElastAlert
    • Integrate Spike with LogDNA
    • Integrate Spike with Zebrium
    • Integrate Spike with LibreNMS
    • Integrate Spike with Uptime Kuma
    • Integrate Spike with Logentries
    • Integrate Spike with Logz
    • Integrate Spike with Ghost Inspector
    • Integrate Spike with Hetrix Tools
    • Integrate Spike with LogRocket
    • Integrate Spike with StatusCake
    • Integrate Spike with Sysdig
    • Integrate Spike with Wavefront
    • Integrate Spike with Buildkite
    • Integrate Spike with Semaphore
    • Integrate Spike with Better Uptime
    • Integrate Spike with Hexowatch
    • Integrate Spike with PM2
    • Integrate Spike with Cloudflare
    • Integrate Spike with Zabbix
    • Integrate Spike with Tenderly
    • Integrate Spike with Xitoring
    • Integrate Spike with Crowdstrike
    • Integrate Spike with GitHub Workflows
    • Integrate Spike with Solarwinds Orion
    • Integrate Spike with Airbrake.io
    • Updown.io
  • Administration
    • Roles and access
    • SSO
    • Enforce login
    • Our notification numbers
    • Contact the support team
    • Adding team members
    • Check if team is getting alerts
    • Removing team members
  • Additional resources
    • Create a badge
Powered by GitBook
On this page
  • Linear
  • How it works
  • Set up
  • FAQs

Was this helpful?

Edit on GitHub
  1. Collaboration
  2. Task management integrations

Linear

The Linear integration with Spike ensures your team’s incident management and task tracking are seamlessly connected.

PreviousClickUpNextShortcut

Last updated 7 months ago

Was this helpful?

Linear

The for Linear automates the flow of incidents, status updates, and comments between both platforms, providing a centralized approach to managing incidents. It streamlines your incident response process, helping resolve incidents faster while keeping everyone in sync.

Main use cases -

  1. Sync incident status with Linear issue status

  2. Sync comments between both platforms

  3. Create issues manually or automatically

How it works

The Spike-Linear integration allows incidents to be sent directly from Spike to Linear, creating a seamless connection between your incident response system and task management. Once an incident is triggered in Spike, it automatically appears as an issue in Linear, where it can be tracked and addressed.

Status synchronization is key to this integration. When an issue is marked as "Done" in Linear, Spike automatically updates the corresponding incident to "Resolved." Likewise, when an issue is moved to "In Progress" in Linear, Spike pauses alerts by marking the incident as "Acknowledged." This bidirectional sync ensures smooth management of incidents across both platforms. Comments made on incidents in either platform are also synced, ensuring your team stays up-to-date.

Incidents from Spike can be sent to Linear manually or automatically using playbooks. All created issues will be automatically synced with Spike's incidents.

Changing an issue from "Done" back to "In Progress" on Linear will not change a resolved incident back to "Acknowledged" in Spike. Similarly, if an issue marked as "In Progress" on Linear is moved back to "Todo," it will not change an "Acknowledged" incident back to "Triggered" in Spike.

At Spike, status changes move in one direction: Triggered → Acknowledged → Resolved


Set up

  1. Manually create issues

Select the incidents, locate the Linear button, and follow the prompts to create an issue.

  1. Automate creating issues

You can link an existing issue from Linear with an incident on Spike to sync both statuses and comments. Multiple Linear issues can be linked to a single incident, and resolving the incident in Spike will automatically mark all associated issues in Linear as "Done."


FAQs

What permissions are needed to connect Linear with Spike?

You will need administrative access to connect Spike with Linear. Once connected, all team members in Spike will have access to create tickets in Linear from incidents in Spike.

What happens if an incident re-opens in Spike?

If an incident in Spike is re-opened after being resolved, the corresponding issue in Linear will remain unchanged unless manually updated.

What happens to comments on Spike if they are made on Linear?

When a comment is made on Linear, it appears in Spike as "Linear commented". Similarly, when someone comments on Spike, it appears in Linear as "Spike commented".

To connect , go to and find the Task Management Integrations section. From there, you'll be guided to connect Linear to Spike. Once set up, all team members across your account can create tickets in Linear directly from Spike.sh.

With , you can pre-configure and automate creating Linear issues. When creating a playbook, select Create an issue on, then Linear, and set up.

Linear
Settings > Organisation
Playbooks
Spike integration
Create an issue on Linear