Low priority development item. Represents a nice to have which we might get too (eventually).

Issue which should be moved into development using a normal process.

This is important, do it now!

Fix it!!! Highest priority issues which are preventing other work from being done.

Low value software feature. May bring some value improvement to the software but it is either niche or "nice to have" in nature.

Moderate value software feature. Solid improvement to the software which will impact many (if not the majority) of users.

High value software feature. Provides a significant improvement to the software and should be scheduled for implementation.

This is so easy to fix, you should probably have already done it.

Fixing the issue is easy, probably an afternoon project.

Fixing the issue provides a moderate challenge. Clear your schedule for the next couple of hours, you've got this!

This is a difficult issue. You will need knowledge of the codebase and it will require a significant amount of time.

Fixing the issue is really hard and requires an investment. The exact causes are unknown, require additional profiling, or a major restructure of the codebase.

This task should be performed by a machine in a repeatable and robust manner.

It's not possible to pursue development of the issue because of problems. Issues that are permanently blocked should be tagged with "Dead."

Vigilance, protection, and security minded

A permanently blocked issue. It might come back to life, but ... it's not likely.

Issues which are currently in a state of planning and preparation, where requirements are being discussed and specifications being written.

Examples, architectural explanations, and reference. Stuff needed to effectively use the software that has been created.

Issue is a duplicate of another issue and adds nothing (or very little) that is new