Labels

• 0 Awaiting End User Feedback

  Notification to the Issue creator that the Core Team require additional information to proceed
• 0 BLOCKED

  Notification to Core Team that Assignee is unable to proceed. Need impediment removed.
• 0 Duplicate

  Notification that this Issue is duplicated elsewhere. Reference should be added to Description
• 0 Help Wanted

  Notification to Core Team that Assignee is seeking assistance, but is able to proceed
• 0 Question

  Notification that Issue has an open question. Please reference open question within Description
• 1a Epic

  High level concept to be addressed. Description should contain a list referencing child User Stories
• 1b User Story

  The User Story details a requirement. It may reference a parent Epic. It may reference child Task(s)
• 1c Task

  Task for team member to perform. Description may contain a Task List and reference child Sub-Tasks
• 1d Sub-Task

  Specific task to perform for referenced parent Task List. Lowest level within category hierarchy
• 2a Discussion Needed

  Prompt for team to discuss at next stand up.
• 2b Gathering Requirements

  Status indicating currently refining User Stories and defining Requirements
• 2c Ready for Development

  Status indicating the Requirements are sufficent to begin designing a solution
• 2d Developing

  Status indicating currently designing and developing a solution
• 2e Ready for Testing

  Status indicating the solution is sufficiently developed to begin testing
• 2f Testing

  Status indicating the solution is being evaluated against the test case(s)
• 2g Final Review

  Status indicating the solution passes the test case(s) and is being reviewed for final acceptance.
• 2h Accepted

  Status indicating the solution passed final review, and is ready for implementation
• 3a Request

  Classification (default) which does not fit as a Feature, Enhancement or Bug. Core Team to evaluate
• 3b Feature

  Classification indicating the addition of novel functionality to the design
• 3c Enhancement

  Classification indicating a change to the functionality of the existing imlementation
• 3d Bug

  Classification indicating the existing implementation does not match the intention of the design
• 4a Low Priority

  Priority indicating minimal impact to system/user -OR- an inexpensive workaround exists
• 4b Normal Priority

  Priority indicating the moderate impact to system/user -OR- existing workaround is costly to perform
• 4c High Priority

  Priority indicating significant impact to system/user -OR- workaround is prohibitivly expensive
• 4d Critical Priority

  Priority indicating system stoppage may occur and no workaround exists
• 5a Docs Needed

  Status specific to Documentation indicating the need for proper documentation to be added
• 5b Docs In Progress

  Status specific to Documentation indication they are currently being refined
• 5c Docs Complete

  Status specific to Documentation indicating they demonstrate the intended design as implemented
• 6 API

  Impact flag identifying the application programing interface (API)
• 6 Build

  Impact flag identifying the build process