GitLab

Stuff that we know we need to work on, but haven't prioritized yet.

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

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

Product team has finished the commercial assessment, ready to handoff.

How does a feature fit into the broader software? How do users enter and leave? How do we onboard and offboard?

We understand how something is going to work, but how is going to function, look, and feel?

What are the real-world needs? What sorts of considerations do we need to look at?

It's not clear where a particular feature or piece of functionality fits into the broader market/picture. Could someone please look at that?

Task requires frontend JavaScript and React development skills

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

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

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

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

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).

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

The feature has been implemented and is waiting to be reviewed or otherwise just hanging out. (Another way of saying, almost done.)

Currently being worked on, expect updates soon ...

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