GitLab

The issue has been implemented, prepared, and packaged. It is currently waiting on the results of testing (unit, integration, functional, or production) before being closed. Basically, really almost done (for real).

Big picture discussions, clarificiations, and direction. “Where do we want to go?” rather than, “How do we get there?”

Issues that are currently in the planning stage

Issues that will be tackled at some future point (probably in a month)

Issues that are queued to be worked on now (but are not currently in development)

Describe how something should be done so that when you start, you don't make a mess

The issue is currently in staging and requires review, or has appeared as part of quality assurance and needs to be addressed.

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 feature has been implemented and is waiting to be reviewed or otherwise just hanging out. (Another way of saying, almost done.)

Involves the operations of the technology. Might be related to platform, configuration, or runtime environment.

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

Currently being worked on, expect updates soon ...

Task requires frontend JavaScript and React development skills

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

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

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

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

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