Any issues that don't pertain to the day-to-day work but rather process related

This label indicates that the issue won't affect the release build

Any issues that require changes to the underlaying architecture

This label indicates that an issue doesn't require any prior knowledge of the code.

Any issues that we agreed we're going to be working on and where we need to understand what to build and why.

Any issues that either are ready for a QA or Dev to confirm the proposed solution or are actively being reviewed.

Any issues that either are ready for development or are actively being worked on by one of the devs.

Any issues that either are ready for code review or are actively being reviewed on by one of the devs.

Any issues we're testing the feature change(s). Not to be confused with release QA which is done when we have a release candidate.

Buffer state for any issues that are waiting to be translated by a localization manager.

Any issues that have been completed and are just waiting to be included in an upcoming release candidate.

Any issues where we're translating the strings.

Any issues or epics that have become stale in the meantime - either created too long ago or we no longer want to tackle.

Issues that are being further refined and will be moved into the Accepted column once we agree to work on them. When issues have this label, they're waiting to be assigned a priority and effort label.

Any issues where we're defining what we're trying to build and how, whether it's creating the design & copy, doing user research, creating the specs, etc.

All work that pertains to any of the ABP products

Any issues that we wish we'd get to but we'll get to them assuming we have the bandwidth, if at all.

Any issues that have a normal priority. These issues are usually UX improvements, or anything that's just part of daily business (e.g. Privacy Policy changes, updating wording in the products, etc.).

Any issues that have a medium priority.