Skip to content

Latest commit

 

History

History
73 lines (51 loc) · 4.42 KB

linear.md

File metadata and controls

73 lines (51 loc) · 4.42 KB
Raw
description
The Linear integration with Spike ensures your team’s incident management and task tracking are seamlessly connected.

Linear

The Spike integration 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.

{% hint style="info" %} 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 {% endhint %}

Set up

To connect Linear, go to Settings > Organisation 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.

{% tabs %} {% tab title="Creating issues on Linear" %}

  1. Manually create issues

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

Create an issue on Linear

  1. Automate creating issues

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

{% endtab %} {% tab title="Link existing Linear issue with Spike" %} 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."

{% endtab %} {% endtabs %}

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".