Edit issues
Change Issue details and review what happens when work moves Teams.
Overview
You can edit an active Issue when its Team gives you editing access. Creating the Issue or receiving a shared link does not automatically grant that access. Comments have separate editing controls.
Edit issue title and description
Open an Issue and click its title or description to edit inline. Press Enter or click outside the title to save it. Description changes save automatically as you type, format text, or add content.
Use the property controls to change status, priority, assignee, or labels. If the Issue becomes read-only, check your access to its Team.
Edit from a table with the keyboard
Focus an active Issue row, then press S for status, P for priority, A for assignee, L for labels, E for estimate, Shift+P for Project, or Shift+D for due date. The existing picker opens for that Issue. Estimate requires the Team to enable it. Canceling leaves the Issue unchanged.
These commands target the focused row, even when other Issues are checked. Use Actions to edit the checked selection. Inputs, editors, and open controls keep their own keyboard behavior. See Select issues for navigation and selection keys.
Revert/Restore issue description (coming soon)
Viewing and restoring earlier description versions is (coming soon). For now, use the editor's undo command to reverse recent edits in your current session. Activity records changes to the Issue but cannot restore its description.
Move an issue to another team
Move an Issue to another Team in the same workspace when responsibility changes. Open the Issue's actions, choose Change Team, and select a destination. If it has sub-issues, choose whether to move just the Issue or its subtree. Review the proposed changes, including access changes for a private Team, before confirming.
To move several Issues, select them in the table and choose Actions → Change Team. You need permission in both Teams. The move applies to the entire reviewed selection or makes no changes; if the preview is outdated, refresh it before confirming.
Old Issue IDs and URLs
Moving an Issue gives it a new Team key. Old keys and links still open the current Issue for people who retain access. Comments, Activity, subscribers, and history stay with it; moving the Issue does not grant access to its destination Team.
If an Issue moves while you have it open and you retain access, its address and breadcrumb update while you keep reading. A small notice shows its new key. If you can no longer read it, the Issue content disappears and a generic unavailable message offers a link back to Issues.
Changes in issue properties
| Issue property | Effect | Workaround |
|---|---|---|
| Issue key | Changed | The Issue receives a key for the destination Team. Old links still open it for people who retain access. |
| Status | Mapped | Check the proposed status in the preview; it maps to the destination Team's workflow. |
| Labels | May change | Review the preview to see which labels will be kept, mapped, or removed. |
| Assignee | May be cleared | If the assignee cannot access the destination Team, choose someone with access after the move. |
| Primary Project | Retained | |
| Parent and sub-issues | May be detached | Move the subtree to preserve links within it. Moving only the Issue detaches hierarchy links outside the moved set. |
See Move Issues between Teams for the full preview and privacy behavior.