Labels

It's in the name. BIG stories sit here, these are a major change that will need several sprints. "Epics are the largest chunks of work, often representing a major goal or initiative."

These are changes that affect facets of the game window, i.e. the custom UI mode is code inside of client that affects how the UI is loaded inside the game window. This change would fit in this category.

Investigative research, these should usually generate user stories that are placed into decomp.

User stories are the smallest units of work in agile. They are basically a single unit of work, ideally with a weight of 1-3. These should be about 1-3 days of "work", these help break up the problem into digestible chunks and ensures CI/CD philosophies.

This label is for development "workflows", compilation chains through build tools (Gradle, Maven) and CI/CD pipelines. Pipelines implement automated testing, artifact generation, continuous integration, and continuous deployment.

user stories that are ready to be developed

Larger features that need decomposition

When peer review reveals the need for changes, this label is appropriate, it signals the code is good but needs fixing before being ready to PR into main.

Features currently in development

features finished and ready to merge Acceptance Criteria: Passing Pipeline Peer Reviewed Passing tests

urgent bugs that break the client