Issues

Plan issues in dated cycles, and group them into projects with milestones and a roadmap.

A cycle is a planning period of one week, two weeks or dates you choose, numbered Cycle 1, Cycle 2 and so on. A project groups related issues under its own identifier prefix, with a lead, a start and target date, and milestones. The Roadmap lists the dated projects with how many of their issues are complete.

Get started free

Cycles

Cycles are off until a team admin turns on cycle planning; members who can edit issues then create them. Turning cycle planning off hides the cycles and keeps them with their issues.

  1. Choose the dates

    A start date and a length of 1 week, 2 weeks or Custom, with an end date. Two cycles in a team cannot overlap, and a cycle's dates cannot be changed after it is created.

  2. Add issues

    Set the cycle on an issue, or select several issues on the Issues list and choose the cycle for all of them.

  3. Follow the cycle

    A cycle's page counts its issues as Completed, In progress and Remaining, then lists them grouped by status. Cycles lists every cycle, newest first, with its dates and how many of its issues are completed.

  4. Carry work over

    Issues stay in their cycle when it ends. Select the unfinished ones on the list and choose the next cycle to move them.

Projects

A project groups related issues in Personal or a team, and an issue can also have no project. Members who can edit issues create projects and change them.

Identifier prefix
Letters and numbers, such as WEB, different from the team's other projects. Issues created in the project are numbered WEB-14 and so on, in the team's one number sequence. The prefix cannot be changed later, and an issue keeps its identifier when it moves to another project.
Overview, lead and dates
An overview in Markdown, a lead who can use Issues, a start date and a target date on or after it.
Status
Planned, In Progress, Paused, Completed or Cancelled. A new project is Planned.
The project page
The overview, lead and dates, then the milestones and the issues. While the page is open, new issues, status changes and completion counts appear without reloading it.
Adding issues
Create an issue on the project's page or choose the project on New issue. Select existing issues on the Issues list to move them in together.

Milestones

A milestone is a named target inside one project.

Details
A name, a description in Markdown, an optional target date and a status: Planned, Active, Completed or Cancelled.
Issues in a milestone
Only issues in the milestone's project can be added. Moving an issue to another project clears its milestone.
Progress
The issue page, the project page and the Milestones page show how many of a milestone's issues are completed.
Removing a milestone
A milestone can be removed once no issues are in it.

The Roadmap

Roadmap is a table of the projects in Personal or the team that have a start date or a target date, earliest first. Each row shows the project's start, target, status and how many of its issues are complete. A project with neither date is not on the Roadmap until one is added.

What counts as completed

Projects, milestones and cycles count an issue as completed when its status is in the Completed category, whatever the status is called, so a Shipped status added to that category counts the same as Done. A cycle counts Started statuses as In progress, and Backlog and Unstarted statuses as Remaining. Team admins choose each status's category.

Client Portal and GitHub

A project can be shared with a client in a Client Portal. The client sees its name, status and target date, not its issues or comments.

A project can link a GitHub repository, and issues in the project can then list pull requests and commits from it.

Plan your first project.

Create a Magpie account, open Issues and create a project under Projects.

Create account