update-ticket

Name: update-ticket
Availability: InStock
Author: amotion-ai

Update Linear ticket status via GraphQL mutation using ticket ID and workflow state.

Updated Apr 7, 2026

Search Tags:#automation #workflow #api #linear #status #ticket

Ready to run

npx skills add https://github.com/amotion-ai/botassist --skill update-ticket-amotion-ai

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: update-ticket
Source: https://github.com/amotion-ai/botassist/tree/main/.claude/skills/update-ticket
Command: npx skills add https://github.com/amotion-ai/botassist --skill update-ticket-amotion-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually changing Linear ticket statuses is time‑consuming and error‑prone, especially when coordinating multiple workflow steps.

Core Features & Use Cases

Argument parsing: Extracts ticket identifier and target status from a single command.
Validation: Ensures the LINEAR_API_KEY is present and verifies the ticket exists.
Dynamic state mapping: Retrieves the team’s workflow states to find the correct state ID.
User confirmation: Shows current and desired status before making any changes.
Automated update: Performs a GraphQL mutation to change the ticket status and reports the result. Use case: A developer finishes a feature and wants to move the associated Linear ticket from Todo to In Review without leaving the chat interface.

Quick Start

Run /update-ticket BSW-123 in-progress to move ticket BSW-123 to In Progress.

Frequently Asked Questions about update-ticket

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I update Linear ticket status programmatically?▼

To update Linear ticket status programmatically, provide the ticket identifier and desired workflow state. The Skill parses these arguments, validates the ticket exists, and applies a GraphQL mutation to transition the status.

Can I move a Linear ticket to In Review using an API?▼

Yes, you can move a Linear ticket to In Review via the API by specifying the target workflow state. The Skill dynamically retrieves the team's workflow states to map the desired status to the correct state ID before updating.

Do I need a LINEAR_API_KEY to automate ticket workflow transitions?▼

Yes, automating ticket workflow transitions requires a LINEAR_API_KEY environment variable. The Skill validates that this key is present before attempting to retrieve workflow states or perform any GraphQL mutations.

What is the command syntax to change a Linear ticket to In Progress?▼

The command syntax to change a Linear ticket to In Progress is `/update-ticket [ticket-identifier] [target-status]`. For example, running `/update-ticket BSW-123 in-progress` moves the specified ticket to the In Progress state.

Does the Skill confirm the status before updating the Linear ticket?▼

Yes, the Skill confirms the status before updating the Linear ticket. It displays both the current and desired workflow states to the user, ensuring verification before executing the automated GraphQL mutation.

What happens if a Linear ticket identifier is invalid during a status update?▼

If a Linear ticket identifier is invalid during a status update, the validation process fails. The Skill verifies that the ticket exists before proceeding with dynamic state mapping or attempting to change the workflow status.