Labels

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.

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.

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

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

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.

In need of descriptions, discussions, and documentation.

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

Fixing the issue is easy. In fact, you should have done it already.

A really nice to have thing to have ....

An issue or merge request that is being used for feature work. It will be closed during a comprehensive review that is part of hand-off.

Currently being worked on, expect updates soon ...

The feature has been implemented, in-review, and has has been accepted for merge. It now just needs someone (always a someone here) to formally accept the changes into the targeted branch. (This label is attached to Merge Requests, not Issues or Work Packages.)