Categories & actions
The company-scoped lookups beside change notices: the category list and reusable action-task templates, plus linking a task to Linear.
The Items navigation contains two company-scoped change-notice configuration lists. Editing either requires parts permission.
Change notice categories
Items → Change Notice Types holds the values for a change notice's "Category" field — the same idea as issue types in Quality. Carbon seeds eleven to start: Design Improvement, Cost Reduction, Quality / Reliability Improvement, Supplier / Sourcing Change, Material or Component Change, Obsolescence / End-of-Life, Regulatory / Compliance, Safety, Manufacturing / Producibility, Customer Request, and Documentation Error / Correction. Add, rename, or remove them to match how your shop classifies changes.
Categories support grouping and filtering but do not affect release behavior. Release behavior comes from each affected item's change type.
Change notice actions
Items → Change Notice Actions holds reusable action-task templates — the checklist items a change notice commonly needs. Carbon seeds seven:
- Engineering Review
- Update Drawings / CAD
- Update BOM / Routing
- Cost Impact Review
- Quality Review
- Inventory Disposition (rework / scrap / use-as-is)
- Notify Affected Parties
A new change notice can copy its task list from active templates. Each task records Pending, In Progress, Completed, or Skipped status, plus an assignee, due date, and notes.
Action tasks are freeform, not gates.
Tasks are a coordination checklist, not an approval workflow. A task's status never blocks a stage from advancing or a change notice from releasing — the stages are the only gate.
Because tasks are the workflow side of a change notice rather than its engineering content, they stay editable at the "Implementation" stage, when the drafts and affected items are already frozen. See Implementation freezes the engineering content.
Link a task to Linear
An action task can link to a Linear ticket, using the same workflow as quality issue action tasks.
The affordance is a Linear icon on the task row, and it only appears when your company has the Linear integration connected. Once a task is linked, the icon is replaced by the ticket's identifier, so you can see at a glance which tasks are being worked outside Carbon.
Opening the dialog gives you two tabs:
A linked task shows the ticket's title, identifier, state, and assignee, with a link out to the ticket itself and an Unlink button to break the connection. A task holds at most one ticket per provider — the tabs are disabled while a link exists, so unlink first if you need to point somewhere else.
The link is two-way.
Edits to the task's notes in Carbon are pushed to the linked ticket's description. In the other direction, when the ticket changes in Linear, a webhook syncs its status, assignee, due date, and description back onto the Carbon task — so completing the ticket in Linear marks the action task completed here. Whoever is doing the work never has to update two systems.
Jira works the same way, when it's available.
The same task row also offers a Jira icon, with the identical Link Existing / Create New dialog and two-way sync. Jira only shows up when the integration is connected and the server has Jira OAuth credentials configured, so on most installs Linear is the one you'll see.