-
Notifications
You must be signed in to change notification settings - Fork 1
HowToUseThisTracker
A Milestone is a relatively big-picture action plan composed of the detailed sub-milestones and issues that make up the action items needed to complete the milestone.
Milestone names should be understandable by interested parties not familiar with the details of a project.
When a milestone is created, it may be initially populated with a checklist of action items. As work on the action plan progresses, checklist action items may be translated to one or more associated issues. See this example milestone.
As the details of a milestone firm, a due date may be assigned. Since the due date is used by other people for their own planning, it is important to update the due date early if it becomes obvious the schedule is likely to slip.
The tracker software closes a milestone automatically when all associated issues are closed. A milestone with no associated issues can be closed by creating dummy tracker issue and then closing it.
An Issue may be a bug report (i.e. functional problem), a feature request, or an action item tracking a step in a milestone. Milestone tracking issues are usually opened by project managers, while bug reports or feature requests may be opened by anyone.
If a bug report or feature request is for a component being worked on as part of an open milestone, or is a milestone tracker, the issue should be associated with the milestone. That is done while editing an issue by pulling down the Milestone list gear button and selecting the applicable milestone. This can be done by whoever opens the issue, or by anyone working on the project.
Issues need to be closed manually when completed or otherwise dealt with.