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.

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 is a ticket where work began but was not finished. The work was put on hold (likely in a feature branch) and will come back to later. This may be due to the task being blocked, or it may simply be due to the task being delayed.

All new tickets start as this state, implied or otherwise. A developer may add this state to explicitly state the ticket is unverified. An unverified ticket is one we have not agreed needs to be worked on. It will eventually either enter a verified state, or simple be closed as wontdo.

The issue has been verified by a developer as legitimate. It will be worked on and verified tickets are now considered part of the backlog.

This ticket has been decided it wont be done. This may mean the bug has been determined to not be real (cant verify) or the feature is one we have decided we dont want to adopt.

Something that doesnt work as intended.

Anytime a ticket represents a discussion about a subject and doesnt fall into one of the other categories.

An error or improvement needed in the documentation

Any first tier epic. That is, an epic which contains only issues as children and will not have sub-epics.

Some new functionality not present.

A type of Epic which will contain other Epics and possibly issues.