Issues

Take bug reports from anyone through a public form, and review every incoming issue in Triage.

A public issue form lets people outside the team report a bug or ask for something without a Magpie account. Each report, and each issue created through the API, becomes an issue that waits in Triage until a member accepts it, cancels it or marks it as a duplicate.

Get started free

Where incoming issues come from

Triage is the review queue for incoming issues in Personal or a team. Issues created on the website go straight into the workflow and do not enter it. Triage and public forms are on every plan.

Public issue forms
Each report becomes an issue in the backlog, shown with Public form as its creator.
The API
An issue created with an API key, which comes with Pro, enters Triage in the team the request selects.
Teammates
A member who can edit sends an issue in an open status to Triage from the issue's page. An issue that was reviewed can be sent again.

Reviewing an issue in Triage

Triage counts the issues waiting and lists them oldest first, with when each was added, its project, and the reporter's contact email when one was given. Members who can edit choose what happens to each.

  1. Accept

    The issue leaves Triage and keeps its status.

  2. Cancel

    The issue moves to the team's first Cancelled status.

  3. Mark duplicate

    Enter the identifier of an existing issue in the same team, such as MAG-123. The issue is linked to it as a duplicate and moves to a Cancelled status.

  4. Recorded on the issue

    The review is recorded in the issue's activity, and the issue page shows its triage state.

Public issue forms

Members who can edit create public forms. A team can have several, each with its own instructions and project.

Form name
Seen only by the team, to tell its forms apart.
Public title and instructions
The title heads the form, and the instructions, written in Markdown, appear below it.
Project
Optional. Reports will take the project's prefix, such as WEB-31, and appear in the project.
Enable and Disable
A new form is off. Enable starts accepting reports and shows the form's public address to share. Disable stops new reports and keeps the issues already reported. A form's name, title, instructions and project can be changed later.

What a reporter sees

The form asks for a title, a description and an optional contact email, and names the project when the form has one. The reporter needs no Magpie account and sees none of the team's issues. After Send report, the page says the report was sent to the team for review.

The contact email is shown only to members who can edit issues, so they can follow up. A connection that sends many reports has to wait before it can send more, and a disabled form shows Issue form unavailable.

Automation rules and webhooks for reports

An automation rule that runs when a public form is submitted can set a priority or a status on every report, such as High priority. A webhook that sends issue.created sends one for each report, with public_form as its source.

Share your first bug report form.

Create a Magpie account, open Issues and create a public form from the More menu.

Create account