---
updatedAt: 2026-05-28T16:14:39.000Z
agentTools:
  siteIndex: https://support.pagerduty.com/llms.txt
  projectIndex: https://support.pagerduty.com/actions/llms.txt
---

# Linear: Update Priority

> 📘 Availability
>
> This workflow action is available on Business and Enterprise for Incident Management pricing plans. Contact the [Sales Team](https://www.pagerduty.com/contact-us/#contact-sales) to upgrade to an account with this action.

# Description

Update the priority of a Linear issue directly from an Incident Workflow. This action enables teams to automatically escalate or adjust issue urgency in Linear as part of their incident response process, keeping development and operations workflows synchronized without manual context-switching.

# Instructions

1. If you have not done so, follow the instructions to [Create an Incident Workflow](/main/docs/incident-workflows#create-an-incident-workflow).
2. When the instructions prompt you to [add actions](/main/docs/incident-workflows#add-actions), select **this action**.
3. Enter the following **Inputs** and click **Save**.
4. Continue following instructions to **Publish** the Workflow.
5. When the action runs, you will see the **Outputs** listed below.

# Inputs

> 📘 Field References
>
> Fields with the **{+}** icon accept [Field References](https://support.pagerduty.com/main/docs/incident-workflows#field-references), which can be useful for referencing incident data or outputs created in prior workflow steps. To add Field References, click **{+}**, or enter `{{`, and select relevant fields. Refer to the [Field References](https://support.pagerduty.com/main/docs/incident-workflows#field-references) article for more information.

| Name         | Description                                                                                                                                  |
| :----------- | :------------------------------------------------------------------------------------------------------------------------------------------- |
| **Team**     | The Linear team that owns the issue. Select from a list of teams in your connected Linear workspace. Teams are listed in alphabetical order. |
| **Issue**    | The Linear issue priority to update. Issues are scoped to the selected team and listed in alphabetical order by identifier and title.        |
| **Priority** | The new priority level to assign to the issue. Accepted values are `No Priority`, `Urgent`, `High`, `Medium`, or `Low`.                      |

# Outputs

| Name          | Description                                                                                                          |
| :------------ | :------------------------------------------------------------------------------------------------------------------- |
| **Issue ID**  | The unique identifier of the updated Linear issue (e.g., `ENG-123`). Can be referenced in downstream workflow steps. |
| **Issue URL** | The direct URL to the updated issue in Linear. Useful for posting to incident channels or adding to incident notes.  |
| **Priority**  | The priority value that was applied to the issue, confirming the update was successful.                              |

# Examples

**Example 1: Escalate a linked issue on high-severity incidents**

Configure a workflow trigger on P1 incidents for a specific service. Use the Linear: Update Priority action to set the linked issue priority to Urgent, ensuring the engineering team is immediately aware of the production impact.

**Example 2: Auto-triage during incident acknowledgment**

When a responder acknowledges an incident, trigger a workflow that updates the associated Linear issue priority to High, signaling that active investigation is underway without requiring the responder to switch tools.