Issue Properties
Use status, priority, assignee, estimates, due dates, Project links, and labels on Team-owned Issues.
Issue properties help Teams scan, assign, classify, and connect work without moving planning ownership out of Notion or Linear.
To rename an active Issue from a table, right-click its row and choose More properties -> Rename. The shared Issue row menu is used in Team Issues, My Issues, Project Issues, and other active Issue-table contexts. The rename command selects the current title and focuses Rename first, so you can type and press Enter immediately; arrow keys move between Rename and Cancel, and Escape closes the command. The option appears only when the server-projected Issue capability allows editing. The new title is shown optimistically, while the canonical Issue key and URL remain stable.
Available properties
| Property | What it does |
|---|---|
| Status | Tracks the Issue through the owning Team's workflow. |
| Priority | Marks urgency as No priority, Urgent, High, Medium, or Low. |
| Assignee | Assigns one workspace user who is eligible for the owning Team. |
| Estimate | Stores optional Team-scaled effort points for visible Issue work. |
| Due date | Sets one manual calendar deadline for the Issue. |
| Project | Links the Issue to one primary Spec-Driven Development Project in the same workspace. |
| Phase | Assigns the Issue to one stage from its current primary Project. |
| Labels | Applies workspace labels and accessible labels from the owning Team. |
In Issue table rows, Project, Labels, Estimate, and Due date appear only when the Issue has a value and the property is turned on in Display. Phase appears when the Issue is linked to a Project. To set an empty property, right-click the row and choose it, or open the Issue.
SLAs, relationships, and attachments are separate Issue workflows. For supported multi-row property changes, see Select and bulk-update Issues.
Status
Every Team has its own Issue status list. New Teams receive the default workflow:
| Status | Category |
|---|---|
| Backlog | Backlog |
| Todo | Unstarted |
| In Progress | Started |
| In Review | Started |
| Done | Completed |
| Canceled | Canceled |
New Issues use the selected Team's default status unless you choose a different status during create.
Priority
Issue priority is an Integrity property. It does not mirror Notion priority or Linear priority.
Use priority when the Team needs a lightweight execution signal for sorting, filtering, grouping, and scanning Issue rows.
Assignee
Each Issue can have one current assignee. The assignee picker only lists users the server allows for the Issue's Team and workspace context.
Assignment history, Issue subscriptions, My Issues, and aggregate Activity are available.
Estimate
Issue estimates are optional Team-scaled effort values. They appear in create, detail, Team Issue tables, My Issues, and Project Issue tables when estimates are enabled for the owning Team or when an Issue retains an existing estimate.
Estimate filters, grouping, sorting, and grouped effort details use only visible Issue rows. Private Team estimates and aggregate effort are hidden from non-members unless the value is shown through an explicitly shared Issue.
Estimate changes write Issue Activity. Team estimate setting changes write Team Audit.
Due date
Each Issue can have one manual due date. Due dates appear in create, detail, and Issue table surfaces, and can drive date filters, due-state display, Inbox deadline notifications, and optional email delivery.
Manual due dates are date-only execution fields. SLA-derived deadlines, business-day math, achieved/failed outcome labels, recurring reminders, and snooze remain separate workflows.
Use SLAs with agents
In Integrity AI or a connected agent, ask for an Issue's SLA deadline, risk, length, and source. A rule-based SLA includes the rule's wording; a manually set SLA identifies its source as a person. Completed SLAs retain their achieved or failed result.
When SLAs are enabled, you can ask an agent to set a duration such as 48 hours. This replaces the Issue's due date. Removing an SLA keeps that choice on later edits, so rules do not immediately add it back. You need the same Issue editing access as when changing its other properties. Integrity AI asks you to confirm the proposed change. Agents can set or remove Issue SLAs, but cannot edit SLA rules.
Project
The Project property links an Issue to one primary Spec-Driven Development Project in the same workspace. Use it when an Issue supports or blocks a known Project.
Integrity labels this property Project. Project detail pages use active primary Project links to show a scoped Issues table and issue-derived Progress counts. Those rows and counts include only Issues the viewer can access; hidden private-Team Issues do not contribute. Multi-link Issue relationships, Initiative rollups, sub-issues, and release/readiness rollups are separate roadmap work.
Phase
After selecting a Project, assign the Issue to one of that Project's Phases. Use the property on create/detail/table surfaces, the command or row menu, or press Shift + M when focus is not inside an editable field.
Changing the primary Project clears an incompatible Phase. Assignment, movement, and removal appear in Issue Activity; the assignment does not send Inbox or email notifications. Phase candidate lists, progress, and counts remain display-safe for private-Team and direct-share readers.
Labels
Labels can come from two scopes:
| Scope | Who manages it | Where it can be used |
|---|---|---|
| Workspace | Workspace admins | Any Issue in the workspace |
| Team | Team managers | Issues owned by that Team |
Workspace labels are shared vocabulary. New workspaces receive Bug, Feature, and Improvement as workspace labels, and admins can rename, recolor, archive, restore, or delete them like other workspace labels.
Use History beside workspace label settings to open Workspace Settings -> Audit log filtered to Issue-label configuration. Assignment changes on an individual Issue stay in that Issue's Activity.
Team labels are scoped to the Team that owns them. Private Team labels are not enumerated for people who cannot access that Team.
A label group holds one choice per Issue, such as a Type group with Bug, Task, and Change. Choosing a label from a group replaces the label already chosen from that group. Ungrouped labels, and labels from different groups, can be combined freely. If an Issue already carried two labels from one group before this rule, both stay until someone changes that group's label on the Issue.
Manage workspace labels
Open workspace settings
Open Workspace Settings -> Issues -> Labels.
Choose the scope view
Use the scope filter to view Workspace and teams, Workspace, Teams, or Archived labels.
Create or edit labels
Use New group or New label, then edit names, descriptions, colors, groups, archive state, or row actions from the table.
The workspace labels table can also show accessible Team sections so admins can compare vocabulary across the workspace.
Manage Team labels
Open a Team, then go to Team settings -> Issue labels.
Team label managers can create grouped labels, edit descriptions and colors, archive or restore labels, permanently delete custom labels, and move custom Team labels to the workspace label scope.
Use History in Team Issue-label settings to open that Team's Audit log. The Team audit records configuration changes only; assigning or removing labels on an Issue remains Issue Activity.
Privacy behavior
Direct-shared non-Team users can see display-safe selected Issue properties on the shared Issue. They cannot enumerate a private Team's full status list, Team label vocabulary, assignable roster, or Project candidate list unless they also have the required Team access.