Issue Types

Issue Types

There are four primary types of issues. They are:

• Epic - Characterized by a naming convention such as <issue-number>/epic/<description> and will always accept pull requests from any branches that are the result of issues mentioned within the EPIC.
• User Story - Can be identified by seeing a branch titled <issue-number>/user-story/<description> and is the hub for tasks that must be completed to finish fulfilling this User Story
• Task - Always the smallest bite of a EPIC, but still play a critical role. Will follow the naming convention: <issue-number>/task/<description>
• Bug - These will never have instructions to fix, only instructions to how to replicate a bug and a description of what should be happening instead. The developer that is assigned a bug will need to apply troubleshooting methods to determine a fix. Will be named in the convention of: `/bug/

Opening Issues

It is primarily the Product Owner's job to open up Issues, with the exception of a bug report which should be opened immediately if a bug is found (within a deployed branch such as alpha, beta, development, documentation, or production) by whoever finds it first. Bugs that are spotted before this should be handled before requesting a pull request into alpha.

Open Issues

Developers are encouraged to self-assign tasks if they are looking for something to do. Typically the Product Owner will assign a task to volunteers during a Team Meeting.

Closing Issues

Usually when a branch is opened up tied to an issue, it will set to automatically close that issue if a successful pull request is made against that branch. In any case it is the Product Owner's responsibility to monitor and close issues and should not be a concern to others.