A bounty of $100 for any open-source contributor who provides a MR that solves this issue. Only the MR which closes this issue will be rewarded the full amount.

A bounty of $1000 for any open-source contributor who provides a MR that solves this issue. Only the MR which closes this issue will be rewarded the full amount.

A bounty of over $1000 for any open-source contributor who provides a MR that solves this issue. Only the MR which closes this issue will be rewarded the full amount.

A bounty of $20 for any open-source contributor who provides a MR that solves this issue. Only the MR which closes this issue will be rewarded the full amount.

A bounty of $250 for any open-source contributor who provides a MR that solves this issue. Only the MR which closes this issue will be rewarded the full amount.

A bounty of $50 for any open-source contributor who provides a MR that solves this issue. Only the MR which closes this issue will be rewarded the full amount.

A bounty of $500 for any open-source contributor who provides a MR that solves this issue. Only the MR which closes this issue will be rewarded the full amount.

A ticket for learning a tool or technology that is needed to be able to do future planning and design.

The ticket has been fully implemented, completed, and merged with the source code. This label should only be applied once a ticket is closed.

A ticket that is actively being developed.

A ticket that has had some code completed to implement but is waiting to pass peer review and is not yet merged in.

This ticket's work started but wasn't finished. It's on hold (likely in a feature branch) and will be resumed later, either due to a blocker or a delay.

All new tickets start in this state. A developer may set it to show the ticket is unverified. This means we haven't agreed to work on it. It will either move to a verified state or be closed as "wontdo."