Target Release

Each issue is assigned a Target Release Date which is the expected release for the change. This assignment is based on the severity of the reported issue, source of the reported issue, and customer priority. Tasks will be assigned to each developer and should be started based on the Target Release Date and priority. If the issue does not have a Target Release assigned, it is possible it is deferred to a future release.

Severity

Within a Target Release tasks should be accomplished based on severity. However, new features and change requests should be implemented prior to bug fixing.

Severity is assigned by the Development Manager

1	Fix Immediately	Critical issue causes a system crash, data loss or corruption. The system becomes unstable or unusable. No workaround exists. Items of this nature should be fixed immediately in a patch release.
2	Fix next point release	Problem of a serious nature causes the software to operate in an unpredictable or detrimental manner with a serious adverse impact to the user. Major functionality is missing or broken. Workaround exists but is unacceptable.
3	Fix in point release if possible, incremental otherwise	A moderate problem causes system functionality to degrade with a moderate adverse impact to the user. Minor functionality is missing or broken. An acceptable workaround to the problem exists.
4	Fix next incremental release	The problem is not detrimental to the operation of the system. It is scheduled for correction in a future major release.
5	Fix if Time	The problem is not detrimental to the operation of the system and will be addressed for the proposed version if there is time. Can be deferred to any subsequent version
6	Undecided	Priority or severity has not been assigned yet
7	Rejected	Issue has been reported that has been determined as either not a bug, how the system operates, or has simply been rejected.