List view
Instructions: 1. Create issues to work on. 2. Assign the issue to the milestone. 3. Assign the issue to a user (yourself) Completed Milestone: 1. Create a blog post describing what has been done 2. Tag a release 3. Deployment
Overdue by 9 year(s)•Due by July 16, 2016Instructions: 1. Create issues to work on. 2. Assign the issue to the milestone. 3. Assign the issue to a user (yourself) Completed Milestone: 1. Create a blog post describing what has been done 2. Tag a release 3. Deployment
Overdue by 9 year(s)•Due by July 9, 2016Instructions: 1. Create issues to work on. 2. Assign the issue to the milestone. 3. Assign the issue to a user (yourself) Completed Milestone: 1. Create a blog post describing what has been done 2. Tag a release 3. Deployment
Overdue by 9 year(s)•Due by July 2, 2016Instructions: 1. Create issues to work on. 2. Assign the issue to the milestone. 3. Assign the issue to a user (yourself) Completed Milestone: 1. Create a blog post describing what has been done 2. Tag a release 3. Deployment
No due dateInstructions: 1. Create issues to work on. 2. Assign the issue to the milestone. 3. Assign the issue to a user (yourself) Completed Milestone: 1. Create a blog post describing what has been done 2. Tag a release 3. Deployment
Overdue by 9 year(s)•Due by June 4, 2016•2/2 issues closedInstructions: 1. Create issues to work on. 2. Assign the issue to the milestone. 3. Assign the issue to a user (yourself) Completed Milestone: 1. Create a blog post describing what has been done 2. Tag a release 3. Deployment
No due date•2/2 issues closedInstructions: 1. Create issues to work on. 2. Assign the issue to the milestone. 3. Assign the issue to a user (yourself) Completed Milestone: 1. Create a blog post describing what has been done 2. Tag a release 3. Deployment
Overdue by 9 year(s)•Due by June 11, 2016•5/5 issues closedInstructions: 1. Create issues to work on. 2. Assign the issue to the milestone. 3. Assign the issue to a user (yourself) Completed Milestone: 1. Create a blog post describing what has been done 2. Tag a release 3. Deployment
Overdue by 9 year(s)•Due by May 28, 2016•6/6 issues closed