linear_team_label (Resource)

Manages an issue label scoped to a single Linear team.

For a label available to every team, use linear_workspace_label. The scope is fixed at creation — Linear has no mutation that moves a label between team and workspace scope.

#Example Usage

resource "linear_team_label" "flaky" {
  team_id     = linear_team.engineering.id
  name        = "flaky"
  color       = "#f2c94c"
  description = "Fails intermittently in CI"
}

#Schema

#Required

• name (String) Name of the label. Unique within its team.
• team_id (String) UUID of the team the label belongs to. Changing it replaces the label — issueLabelUpdate has no teamId.

#Optional

• color (String) Colour of the label as a hex string, e.g. #5e6ad2. Linear picks one when unset.
• description (String) Description of the label.
• is_group (Boolean) Whether the label is a group — a container other labels nest under, which cannot be applied to an issue itself. Changing this replaces the label.
• parent_id (String) UUID of the parent label group this label nests under. Set it to "" to unset the reference — leaving the attribute out of the configuration keeps whatever is live, so "" is how a configuration asks for no reference at all.

#Read-Only

• id (String) UUID of the label.

#Import

Import is supported using the following syntax:

The terraform import command can be used, for example:

# Import by UUID.
terraform import linear_team_label.example a1b2c3d4-0000-0000-0000-000000000000