Labels

[Progress captain: None] The problem is recognized and understood. Anyone can pick up the issue.

[Progress captain: assignee & creator of the issue/project owners/maintainers/.developers/community] The relevant parties are working to propose and converge on a particular solution/implementation. Issue must have at least one assignee.

[Progress captain: assignee] The solution is clear. Anyone can pick up the issue implementation.

[Progress captain: assignee] The current assignee is actively working on fixing the issue according to the agreed-upon solution and creating a Merge Request.

Something is blocking progress on this issue due to problems external to this repository. This should be clarified in the issue.

Something is blocking progress on this issue in the same repository. This should be clarified in the issue.

The maintainers have decided not to address this issue. The reason should be stated in the issue discussion.

Any variance between actual and expected result, can include bugs in the code or defects in the documentation or visualization.

A new feature or enhancement of an existing feature.

Code refactoring of existing functionality.

This issue has critical priority and must be worked on ASAP to go into a hotfix release (if necessary). Git cherry-pick or file checkout can be used for this.

This issue/MR is key for the associated milestone and must be completed before the deadline of the milestone. Some will be associated with a milestone without this label because they are not blocking the release (e.g. external feature contributions).

Issue flagged suitable for unitaryhack event.

Issue with unitaryhack bounty.