Create and edit
Create an issue from a team’s issue list. Add a title and description, then confirm the team and assignee. Details let you change status, priority, labels, project, cycle and dates. The description editor has a format menu and a selection toolbar, with Markdown, slash commands and keyboard shortcuts. Check the saved result; a draft remaining in an editor does not prove it reached the server.
In both dialog sizes, scroll the form while the header and the Create issue, Cancel, and Create more controls stay in view. Status, priority, and assignee are visible by default. Open More properties for project, labels, due date, parent issue, and release. Expanding or collapsing keeps your text and attachments. Submit with Cmd/Ctrl+Enter. Esc closes an open picker first.
Issue identifiers are unique within a workspace. Detail links can use the current identifier (for example, /demo/issues/ENG-1); old identifier links redirect to the new identifier after a team move. Internal ID links still work, and integrations should prefer the API-returned internal ID for writes. Team identifiers cannot be reused within a workspace, even after a team is deleted, to preserve historical issue links.
On narrow issue pages and in Inbox details, change status or assignee directly below the title, or open Properties for the other fields. Press Esc to close the current picker first and then the property drawer. Use Comment actions beside a comment for available actions such as editing, deleting, or resolving a thread.
Status and priority
Status describes the stage of work; priority describes its order. Teams can configure their default creation status, while an explicitly selected status takes precedence. Only the completed category counts toward completed work. Cancelled and duplicate issues do not. Completing an issue again after reopening creates another completion event.
Do not use labels as a substitute for status or urgency as a substitute for ownership. Before bulk updates, check the selection and inspect any failed results afterward.
Work directly in lists and boards
Click assignees, statuses, priorities, and labels directly in team, workspace, and project issue lists and boards, as well as cycle details, project overviews, and sub-issue lists. Displayed project, date, estimate, and cycle fields also support inline editing. Clicking a property changes only that issue; the title or row background opens its details. Issues that no longer match a view leave it; My issues retains its existing temporary handover behavior.
On narrow My issues, team, workspace, and project lists or boards, open More properties on an issue to view or edit its displayed project, due date, estimate, and cycle. Status, assignee, priority, and labels remain directly accessible. Breadcrumbs show the current page and relevant parents; use the sidebar to switch workspaces.
In primary issue lists and boards, use J/K or the arrow keys to browse, Enter to open, X to select, Shift + click/arrows to extend a range, and Ctrl/Cmd + A to select loaded, expanded, visible issues. Bulk writes deduplicate issue IDs and do not automatically fetch additional pages. Use S/A/P/L for status, assignee, priority, and labels; I to assign yourself; Shift + D/E for due date and estimate; and H for a personal reminder. Explicit selections take precedence over highlighting. Inputs, IME composition, native controls, and overlays retain their keyboard behavior.
Use the context menu, keyboard menu, bottom bulk toolbar, or Ctrl/Cmd + K command menu. Commands identify their current targets. F opens filters, Shift + V opens display options, Ctrl/Cmd + F focuses view search, and Ctrl/Cmd + B switches list and board. Bulk actions save each issue separately, distinguish confirmed, queued, and failed results, and retain failed targets for retry.
Quick filters and display settings take effect immediately. On narrow screens, open a field in the filter panel and use Back to return to the field list. In My Issues, open Advanced filter to edit multiple conditions. Apply filters commits the draft, Cancel discards it, and Clear advanced filter removes advanced conditions while keeping quick filters. The actions stay visible while you scroll conditions. Press Esc to close one layer and return to its opening control.
Open Views in the toolbar to see the current view and any unsaved changes. Save as new view stays visible while you scroll. Save view changes is available only to the author after edits. When saving a new view, choose whether only you or the workspace can see it. Open a view’s More options to read the full name, and press Esc to go back one layer. Detaching a view keeps your current filters.
Preview and create faster
Press Space on a highlighted issue, or choose Quick preview from its menu, to read its details. On desktop, J/K continues browsing while the preview is open. Esc closes the preview first and preserves position and selection. Narrow screens use a preview drawer. Previewing never writes to an issue or adds it to recent visits.
With no search text, the command menu shows up to 20 recently opened issues from the current login and workspace. Visits are not retained across refreshes or devices, and are cleared on logout or workspace changes. Inaccessible issues are not shown.
Use the arrow keys to browse commands and Enter to run the highlighted command. Press Esc or select Close to leave the menu. In view search, Clear search clears the text and keeps focus in the field; Esc closes search and returns focus to its button. In Inbox, press Esc once to dismiss suggestions and again to clear the search text. Applied filters stay in place.
Create buttons in group headers and board columns prefill explicit group properties while respecting the page’s fixed team and project. Ambiguous cross-team statuses require choosing a team first. Select text in an existing issue description and choose Create issue from the formatting toolbar or menu: the first nonempty line becomes its title, and the full selection plus a source link becomes the description. The new issue inherits team and project without deleting source text, copying attachments, or automatically becoming a sub-issue.
Manual ordering affects other workspace members and views. Boards persist relative positions only with manual ordering or within the same priority tier when ordered by priority. Other automatic orders cannot be overridden by dragging. Moving across statuses still updates the status. If properties succeed but ordering fails, inspect the refreshed result.
Team triage
Open Triage beneath a team in the sidebar. The queue lists incoming issues newest first, with title/identifier search, priority and assignee filters, and pagination. Desktop shows details beside the queue; narrow screens open details after selecting an issue.
Create an issue using the top-right button, C, or the command palette. Creation defaults to the current team’s Triage status, ahead of its normal default and an existing draft; you can still select another status. Filters live beside search, and secondary actions appear under More triage actions on narrow screens.
With an issue selected, press 1 to accept, 2 to open rejection confirmation, or 3 to choose the original issue for a duplicate. Processing shortcuts are inactive while typing, composing text, using a dialog or menu, or saving. Rejecting and marking duplicates still require confirmation. Queue selection, search and filters are temporarily disabled while submitting and refreshing the result, then become available again. Press ? for shortcut help.
Anyone with issue edit access can accept, reject, mark duplicate or transfer one issue at a time. Accept moves it into the team’s configured Backlog or To Do status. Reject moves it to the first canceled status and keeps the issue and comments. Mark duplicate requires choosing the original; only the current issue enters Duplicate. Transfer moves the existing issue into another accessible team’s triage queue, applying existing identifier, label, project, cycle and release move rules. Its assignee must be able to access the destination team.
Administrators configure the creation default, acceptance status and notification responsibility under Team settings → Triage. Choosing Triage as the creation default sends new issues without an explicit status context into the queue; an explicit status still wins. Acceptance defaults to the first Backlog status, or a chosen team Backlog/To Do status. Responsible members receive notifications; they are not automatically assigned to issues and do not have exclusive processing rights.
Decisions require a connection. Retry the same request after an uncertain result. If someone else processed the issue, the page reports a conflict and reads its current state. Private-team access remains enforced, including for workspace administrators. Workspace-wide aggregation, bulk actions, snooze, rotation and automatic assignment are not included.
Descriptions, relations and attachments
Keep context and acceptance criteria in the description and discussion in comments. Use sub-issues and blocking relations to describe dependencies. Relations do not promise automatic scheduling or status changes for every related issue.
Attachments require administrator-configured storage and remain subject to current issue access. A pasted, dropped or selected image first appears at its insertion point, then resolves when upload completes. Text, images and attachments undo and redo together. The attachment list shows thumbnails and names and can locate an image in the description. Removing the last description reference to an unsubmitted image also removes its draft attachment; removing a saved image from the description keeps the attachment. Wait for, retry or remove unfinished uploads before submitting or leaving. If uploads are unavailable, ask your administrator. An external public file link does not provide the same access guarantees as a private attachment.
Dates, cycles and releases
Start and due dates belong to the issue. A cycle is a team’s planning window. Adjusting an issue’s dates on the timeline does not change the team cycle or remove cycle membership.
An issue can target one planned release in its current project. Moving or clearing its project, deleting it or invalidating team relationships may clear the current release association. Frozen publication history is independent. See Project releases.
Activity and failed saves
Activity helps explain real changes but is not an authorization check or a complete reconstruction of every historical state. If saving fails, keep your draft, reconnect and re-read the issue before retrying. Creating issues and comments is not automatically deduplicated; repeated submissions can create duplicates.
Team, status and project changes use names from the directories you can currently access. Renaming a resource also updates its name in past activity. Pending, deleted or inaccessible names appear as “Unknown” instead of internal IDs. If a former team’s status names fail to load, retry within Activity; your comment draft stays in place. Cycles, milestones and releases keep their recorded name snapshots.