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

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.

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

Task requires frontend JavaScript and React development skills

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

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

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?

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

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

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

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

A specific use-case or set of criteria that needs to be captured in a test (which is preferably automated).