How Watching for Issue Updates Actually Works in Linear
This uses Linear's webhook system to push an event whenever a tracked issue changes, rather than requiring an automation to poll and diff issue state itself.
Real API Details
The webhook payload for an update generally reflects the issue's current state along with the change, which matters for distinguishing something routine (like a status move within the team's normal workflow) from something that needs an actual response (like a reassignment or priority change).
Practical Considerations
Because a single edit in Linear's UI can sometimes trigger multiple underlying field changes at once, an automation reacting to updates should check which specific fields it actually cares about changed, rather than treating every update event the same way.
Use cases
Synchronize downstream systems with issue state changes
- Auto-notify teams on status updates
- Adjust SLA calculations on modifications
- Trigger reallocation when priorities change
- Log change history for audits