Create and track issues
Create an issue, change it on its page, and comment on it, link it to other issues and attach files.
Issues are records for bugs, features and other product work. Each issue has
an identifier such as MAG-12, a status and a priority, and can have an
assignee and a due date. For a board with columns you name yourself, use Track work with Kanban boards
instead.
Open Issues from the navigation to see the issues in Personal or the selected team. The Issues section of the sidebar also has Projects, Board, Roadmap, Triage, Notifications, Saved views, Statuses and Webhooks. Other tasks have their own articles:
- Search, filter, the board, saved views and changing many issues at once: Issue list, board and saved views
- Projects, milestones and the Roadmap: Issue projects, milestones and roadmap
- Cycles: Plan issues in cycles
- Triage and public forms for reports: Triage and public issue forms
- Statuses, custom fields and automations: Issue statuses, labels, custom fields and automations
- Subscriptions, mentions and email: Issue notifications and email
- CSV, JSON and GitHub imports and exports: Import and export issues
- Webhooks: Issue webhooks
Who can change issues
Every member who can use Issues in a team (see Choose the areas a member can use) can open its issues, comment, subscribe and export. Team admins can create and change issues, and so can other members when the team's Member access setting lets members edit (see Create and manage a team). In Personal you can do everything. Team admins manage statuses, cycle planning and webhooks. An issue can be assigned to any member who can use Issues in the team.
Create an issue
Choose Create issue on the Issues list, the Board or a project's page. You can also press C outside a text field, or find Create issue in the command palette.
New issue opens beside the page. The issue will be created in Personal or the selected team.
- Enter a title.
- If the team has projects, choose a project, or leave No project. On a project's page, that project is already chosen.
- Choose Create issue.
The issue starts in Backlog with no priority, and its page opens, where you set everything else.
To put the issue in a project that does not exist yet, choose Create a project under Create issue. Once the project is created, New issue opens again on the project's page, with the project chosen and your title kept.
Issues in a team share one number sequence. An issue created in a project
takes that project's prefix and the others take MAG, so a team can have
MAG-1, then WEB-2 in a project with the prefix WEB. An issue keeps its
identifier for good, even when it moves to another project. To find an issue
by its identifier, type the whole identifier into the search box on the
Issues list.
Change an issue
An issue page shows the title, the identifier and project, then the properties: Status, Priority, Assignee, Due date and Labels, and Milestone, Cycle, Triage and custom fields when they apply. The description follows.
Members who can edit change each property where it is shown, and each change saves at once:
- Status, Priority, Assignee, Milestone, Cycle, and a Select or User custom field: choose the current value, then another. None clears it.
- Due date, and a Text, Number or Date custom field: click the value, change it and press Enter.
- A Checkbox custom field: turn its switch on or off.
- Labels, and a Multi-select custom field: choose Change beside it, tick what the issue should have, and save.
Milestone is offered once the issue's project has milestones, and Cycle while the team plans in cycles (see Issue projects, milestones and roadmap and Plan issues in cycles).
The priorities are No priority, Urgent, High, Medium and Low. Moving an issue to a status in the Completed category records the date it was completed, and a Cancelled status records the date it was cancelled. Moving it back to another status clears that date.
An issue stays assigned to someone who has left the team, is on leave or can no longer use Issues, until it is assigned to someone else or unassigned. The Assignee shows their name with "no longer in the team", and the issue's other properties can still be changed.
Click the title to change it, and press Enter to save. Click the description to change it: Enter starts a new line, Ctrl+Enter (Cmd+Enter on a Mac) or a click elsewhere saves, and Escape cancels. Links in the description still open when clicked. Descriptions use Markdown, including headings, lists, code blocks and links.
If someone else saves the title or description while you are changing it, your change is not saved over theirs. Your text stays open in the field: save it again to replace theirs, or press Escape to keep theirs.
Saving labels or a Multi-select field changes only the boxes you ticked or cleared. A label someone else added after you opened the list stays as they left it.
To move an issue to another project, select it on the Issues list and choose Project in the bar above the list (see Issue list, board and saved views). Its milestone is cleared, because a milestone is part of one project.
While an issue page is open, it updates when another member changes the description, properties, comments or activity.
Labels
Labels are shared by the whole team, and a label can be added to any number of issues. To change an issue's labels:
- Choose Change beside Labels on the issue's page.
- Tick the labels the issue should have, and clear the others.
- Choose Save labels.
Create a label…, under the list, makes a new label by name and puts it on the issue. Labels show beside the title on the Issues list. The team's labels are renamed, described and deleted on Labels (see Issue statuses, labels, custom fields and automations).
Comments and activity
The Activity section lists comments and changes together, oldest first: creation, edits, status and other property changes, label changes, and comments removed or restored. Each change is one line naming the person and the time.
Write a comment in the box at the end of Activity and choose Comment.
Comments use Markdown. Write @ and a member's handle to notify them (see
Issue notifications and email).
Edit or remove a comment
The author of a comment and team admins see Edit and Remove beside it.
- Choose Edit. The comment becomes a box holding its text, where it is.
- Change the text.
- Press Ctrl+Enter (Cmd+Enter on a Mac), or click away, to save it.
Escape puts the comment back as it was. A saved comment is marked Edited.
If someone else changed the comment while you were editing, your text stays in the box. Save it again to replace theirs, or press Escape to keep theirs.
Remove takes the comment off the issue at once. The message that follows offers Undo, which puts the comment back.
Related issues and sub-issues
Choose Link an issue below the description. In the drawer, choose whether
this issue Is related to, Blocks or Is a duplicate of another
issue, and enter that issue's ID, such as MAG-123. The other issue shows the
link as Blocked by or Duplicated by.
To make this issue a sub-issue, enter the parent's ID under Parent issue and choose Save parent. Clear the field to remove the parent.
Related issues on the issue page lists the parent, the sub-issues and the links, and counts how many sub-issues are complete. Choose Remove beside a link to remove it. Both issues must be in the same team, an issue cannot be its own parent, and a parent chain cannot loop back on itself.
Attachments
Choose Attach files below the description. Choose files, drop them, or paste an image, and choose whether to attach them to the issue or to one of its comments. Each file can be up to 25 MB. Images show a preview on the issue page. Attachments can be opened only by people who can see the issue, and members who can edit can remove one with Remove.
GitHub pull requests and commits
When the issue's project is linked to a GitHub repository (see Issue projects, milestones and roadmap), the issue page has a Development section. It suggests a branch name made from the identifier and title, with Copy. Choose Add a pull request or commit, then enter its GitHub address, which must be in the project's repository, and optionally a title and branch name. More, then Copy branch name, copies the suggested name on any issue.
Magpie keeps these links. It does not read pull request status from GitHub or create branches in GitHub.
Time spent on an issue
Start timer beside the issue's name starts a Time Tracking timer linked to the issue, with the issue's title as its description, and you stay on the issue. Your time in the properties shows the time you have recorded on the issue. See Track time.
Move an issue to Trash
Members who can edit choose More, then Move to Trash. API users with
team edit access can do the same with DELETE. The issue is kept in the team's
Trash for 30 days and can be restored with its
comments and history; after that it is deleted for good. If its status,
milestone, cycle or project was removed in the meantime, the restored issue
comes back with the workflow's first status, or without the removed
milestone, cycle or project, and the message says so.
In the Magpie app
Issues in the app lists the issues in Personal or the selected team, newest change first. Search from the header. Filters above the list opens the view (such as My Issues or Backlog), status, priority, project, label and sort; the row names what is applied, and Save as view… keeps it as a saved view. Choose New to create an issue.
The header's menu opens the other Issues pages: Board, Projects, Roadmap, Cycles, Triage, Notifications, Saved views, Statuses, Labels, Custom fields, Public forms, Automation, Webhooks (team admins) and Trash. On the board, statuses are listed one under another; hold an issue and choose Move to a status. In Triage, hold an issue to accept it, mark it as a duplicate or cancel it. In Statuses, hold a status to move it up or down.
On an issue, tap the title, Status, Priority, Assignee, Due date, Labels, Milestone, Cycle or a custom field to change it. Each change saves at once. The issue's menu has Subscribe, Start timer, Copy branch name, Link an issue…, Set parent issue…, Attach files…, Send to Triage and Move to Trash. Attach files from Files, your photos or the camera, to the issue or to one of its comments; tap an attachment to open it, or swipe it to remove it. Related issues, GitHub links and the activity are listed on the issue, and your own comments have Edit comment and Remove comment.
The app does not import or export issues, change several issues at once, or group the list.
For help with issues, Contact support.
Ask Magpie support
Send Magpie staff a question about anything this article does not answer.