We Enhance IT Standard Tags for GitHub Issues

We Enhance IT uses the GitHub issues to collaboratively mange the development and support of applications.

In order to help developers efficiently use and review outstanding issues, each issue must be assign a single tag from the following list. The list defines the meaning of each tag.

• Bug This tag indicates the issue is the documentation of an error detected in a released version of an application. The issue should fully describe all known information on the bug, including a description of how the problem manifests itself, under what circumstances the bug is detected, the seriousness of the bug and the urgency of the delivery of a solution.
  A Bug must be assigned a responsible person.
  In general a Bug will be assigned a milestone that is the release that will resolve the bug. Should the problem be deemed non-critical and to be addressed in a future release, the issue may be changed to a Task with a milestone of the anticipated release that it will be resolved with.

• Enhancement This tag indicates the issue is the documentation of an idea for new functionality for a future release.
  An Enhancement issue is not generally assigned a responsible person, nor is it assigned to a milestone. It is merely a documented suggestion for future functionality. Once the idea is accepted as functionality for a future release, its tag would be changed to Specification

• Task This tag indicates that the issue describes a set of work that must be completed before a milestone may be considered complete. Generally, a set of tasks must be completed in order to implement a Specification. However, tasks may be required to investigate technology, set up production environment, get use cases from a customer or complete any kind of work required to complete the release.
  A Task must always be assigned a responsible person and a milestone.

• Specification This tag indicates that the issue describe a set (or sub-set) of functionality that is associated with a planned release of an application.
  Generally, Specification is not assigned a responsible person, as the functionality is usually implemented with a set of one or more tasks. However, should the Specification be clearly implemented with a single task - the issue would be assigned a responsible person in lieu of creating an associated task.
  A Specification is always assigned a milestone

• Review This tag is a call for input from other team members and may be a request for help, a request to review a document, a request to review some code, etc.
  A Review is not assigned a responsible person, but must be assigned a milestone. These issues are not intended to be active for a very long period of time. This kind of issue should be reviewed by other team members as quickly as possible, feedback provided and then closed.