How sync works
When you move a Linear issue from one state to another — for example, from Todo to In Progress — Linear notifies NOCK of the change. NOCK then updates the status of the linked ticket to match. The update typically appears in NOCK within a few seconds of the change being made in Linear.Status sync is one-directional: changes made in Linear update NOCK. Changing a ticket status directly in NOCK does not push an update back to Linear.
Status mapping
Linear uses customisable workflow states, which NOCK maps to its own fixed set of statuses. The table below shows the default mapping.| Linear state category | NOCK ticket status |
|---|---|
| Backlog / Unstarted | Open |
| Started | In Progress |
| Completed | Resolved |
| Cancelled | Closed |
Linear allows teams to create custom state names (for example, Scoping, Code Review, Waiting on Customer). NOCK maps these to the closest status based on their underlying state category in Linear, not the display name. As long as you keep states in the correct Linear category, the mapping will work as expected.
Sync timing
Status updates are near real-time. In most cases the NOCK ticket status reflects the Linear issue state within seconds of the change. If you make several rapid status changes in Linear, NOCK will reflect the most recent state once it processes the updates.What customers see in the Customer Portal
Customers who have access to your NOCK Customer Portal see ticket statuses displayed as human-readable labels — Open, In Progress, Resolved, or Closed. They never see your internal Linear state names, Linear links, or any other project-management detail. As your team works through issues in Linear, the Customer Portal updates automatically, giving customers confidence that their feedback is being acted on — without requiring any communication effort from your team.Connect Linear
Set up the Linear integration if you haven’t already.
Troubleshooting
Fix common issues with status sync and the Linear connection.