Create Issues
Create Issues from workspace or Team context with a title, collaborative document, and Team-owned property values.
You can create Issues from workspace context or from a specific Team Issues page.
You need access to the selected active Team. Team members can create Issues in Teams they can access without being workspace admins.
An enabled public Team may instead offer Submit issue for review to a workspace member outside the Team. That reduced Triage form accepts only Team, title, and description; it does not grant normal Issue creation or editing. See Team Triage.
Workspace create
Use the sidebar create action to open the full-page Issue create route:
/workspace/{workspaceId}/issues/newThe form includes an accessible Team selector. Integrity preselects a safe active Team when it can, but you can choose another Team before creating the Issue.
Team create
From a Team Issues page, use the Create issue action or the empty-state call to action. The Team-context modal starts with that Team selected and keeps you on the Team Issues page after creation so the new row appears in context.
From a Feature detail Issues tab, use the Issue create action to open the same Team-context modal with the current Feature already selected. The new Issue appears in that Feature's Issues table after create when the Feature link is valid for your workspace and permissions.
Create beneath a parent Issue
From an Issue detail page, use the Sub-issues section to create a normal Issue beneath the current parent. The Team and parent stay fixed. Priority and the primary Feature are inherited as editable defaults, and the assignee is inherited when that person remains assignable. Labels are not inherited.
You can also set or change an existing Issue's parent from its actions. Parents and children must remain in the same Team, and Integrity rejects cycles. See Issue hierarchy and sub-issues.
Required fields
| Field | Behavior |
|---|---|
| Team | Required. Must be an active Team you can access. |
| Title | Required. Trimmed and limited to 200 characters. |
| Description | Optional rich document content. Supports the same blocks, formatting, slash commands, toolbar, and keyboard controls as Feature and Initiative documents. |
| Status | Required. Defaults to the selected Team's default status. |
| Priority | Optional. Defaults to No priority. |
| Assignee | Optional. Lists assignable users for the selected Team. |
| Estimate | Optional. Uses the selected Team's effective estimate scale when estimates are enabled. |
| Feature | Optional. Links one primary Feature in the same workspace. |
| Labels | Optional. Lists workspace labels and accessible labels from the selected Team. |
Successful creation confirms the assigned Issue key with a toast. Integrity does not automatically route to the new Issue detail page.
Integrity validates the selected status, priority, assignee, estimate, Feature, and labels before returning success. If a selected value is not allowed, creation fails without leaving a partial Issue behind.
The create dialog keeps the document draft locally until the Issue and its primary document are created together. Use the expand control for long-form content; the dialog grows while its header and footer stay fixed. Press Ctrl+Enter or Command+Enter to create the Issue. Enter inside the document inserts content normally. File uploads become available after creation, when the persisted collaborative document opens.
Use the ellipsis menu and choose Add sub-issue to draft children before creating the main Issue. The child editor opens first. After you add the first child, it becomes a row in the Sub-issues overview, where you can add, edit, or remove drafts. Draft rows show Pending where the final Issue key will appear; Integrity assigns the real Team Issue key only after creation. Finish or cancel the open child editor before creating the main Issue. When you submit, the main Issue is created first and retained child drafts are then created beneath it.
If a child cannot be confirmed after the main Issue is created, Integrity keeps that child draft and its attachments in the dialog. Review the remaining drafts and choose Retry sub-issues; the confirmed parent is not created again. Remove a draft or cancel the dialog only when you want to discard its staged attachments.
Changing the selected Team refreshes Team-specific status, assignee, estimate, Feature, and label options. A Feature preselected from a Feature Issues tab stays selected while the new Team data loads; Integrity validates it again on submit and rejects values you cannot use.
Editing after create
On the Issue detail page, Team members with access to the owning Team can update the title, collaborative Description document, status, priority, assignee, estimate, Feature, labels, and icon color. Users without Team Issue work access can still read Issues they are allowed to see, but the server rejects direct mutation attempts.
Direct Issue shares are read-only in this release. A direct-share recipient can open the shared Issue without gaining Team context, private Team option lists, or Team Issue edit rights.
Managing labels
Team members can apply existing labels to Issues they can edit. Creating, renaming, grouping, archiving, restoring, deleting, or moving Team label definitions follows the Team's Label management policy.