Issues
Magpie tracks your team’s bugs and product work as issues. It plans them in projects and cycles, and takes bug reports from outside.
Issues is Magpie’s issue tracker. Each issue keeps an identifier such as MAG-12, a status, a priority and an assignee. Your team can work in a list or on a board of its own statuses.
Create account
Each issue keeps its identifier, and your team works in a list or on a board.
Each issue has an identifier such as MAG-12 that it keeps for good. It also has a status, a priority, an assignee, a due date and labels. Its page holds Markdown comments, files, sub-issues and links to related issues.
You can search, filter and group the list, and save it as a view. On the board, you drag issues between statuses. Each team sets its own statuses, custom fields and automation rules.
Cycles and projects plan the work, and the Roadmap shows the dated projects.
A cycle is a dated planning period of one week, two weeks or your own length. Its page counts the completed, in-progress and remaining issues. Unfinished issues can move to the next cycle together.
A project has its own identifier prefix, a lead, start and target dates, and milestones. The Roadmap lists the dated projects with how many of their issues are complete.
Anyone can report a bug on a public form, and each report waits in Triage.
A public form lets anyone report a bug without a Magpie account. Reports, and issues created through the API, wait in Triage.
You accept each report, cancel it or mark it as a duplicate. A form can send its reports to a project. Only members who can edit issues see the reporter’s email.
You can import and export issues, and send each change to your own software.
One import brings in up to 200 issues. It reads a CSV file or a GitHub Issues export. You can export every issue as CSV, or as JSON with comments and activity.
Webhooks send signed issue, comment and project events to an HTTPS address. The REST API lists, creates and updates issues.
Issues tells the people on an issue about changes, and links work to GitHub.
- Subscriptions and mentions
- An issue’s creator, its assignee and everyone who comments are subscribed to it. They are notified when someone else changes it. An @mention in a comment notifies one member.
- Each person chooses which issue email they get, such as mentions, assignments and comments. Issue email is off until they turn it on.
- GitHub pull requests and commits
- A project can name its GitHub repository. Its issues then list pull requests and commits by their addresses, with a suggested branch name. Magpie does not read their status from GitHub.
- Projects in Client Portal
- A project can be shown to a client in Client Portal. The client sees its name, status and target date, not its issues or comments.
Plans
Issues is on every plan, with no limit on issues or projects. The REST API needs an API key, and API keys come with paid plans.
Questions
Who on the team can change issues?
Every member who can use Issues can open its issues, comment and export. Team admins create and change issues, and so do members when the team lets members edit. Team admins manage statuses, cycle planning and webhooks.
Can rules set an issue’s priority or status for us?
Yes. An automation rule runs when an issue is created, changes status or gets a label. It can also run when the assignee changes or a public form sends a report. The rule then sets a priority or a status. A rule that gives every public report high priority is one example.
Can I see what happened to an issue?
Yes. Each issue’s Activity lists its comments and changes together, each with the person and the time. An issue moved to Trash can be restored with its comments and history for 30 days.
What happens when two people change the same issue?
An open issue page updates when someone else changes it. Someone may save the title or description while you are editing it. Your save then does not replace theirs. Your text stays in the field, so you can choose which to keep.
Can I bring our issues over from GitHub?
Yes. You save a repository’s issues as JSON with GitHub CLI and upload the file. Each issue keeps its GitHub number as its original ID. Its title, body, labels and first assignee come with it. Open issues go to Backlog and closed ones to a completed status.
Start tracking issues.
Create a Magpie account and add your first issue.