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.

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

Fixing the issue is easy, probably an afternoon project.

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

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.

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

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

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

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

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?

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

Task requires frontend JavaScript and React development skills

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

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

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

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