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.
!!! High Priority
This is important, do it now!
Fix it!!! Highest priority issues which are preventing other work from being done.
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."
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.
Examples, architectural explanations, and reference. Stuff needed to effectively use the software that has been created.
Oak-Tree / Medical Imaging / Oak-Tree Imaging Environment
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.
Frontend / ReactJS
Currently being worked on, expect updates soon ...
Fixing the issue provides a moderate challenge. Clear your schedule for the next couple of hours, you've got this!
Involves the operations of the technology. Might be related to platform, configuration, or runtime environment.
Pending Merge (In-Review)
The feature has been implemented and is waiting to be reviewed or otherwise just hanging out. (Another way of saying, almost done.)
The first time you attempt to do something, you'll get it wrong, so build a prototype first. (Another way of saying we might not know how to do this.)
The issue is currently in staging and requires review, or has appeared as part of quality assurance and needs to be addressed.