Issue with unitaryhack bounty.

Issue flagged suitable for unitaryhack event.

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).

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.

Code refactoring of existing functionality.

A new feature or enhancement of an existing feature.

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

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

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

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

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

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

[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: None] The problem is recognized and understood. Anyone can pick up the issue.

[Progress captain: creator of the issue] The problem in the new issue is not reproducible and/or not clear enough to allow for the design of a solution.

Old ticket with no recent updates: not closing as there is still potential value -- it will however not actively be tracked by maintainers when this label is on.

This is requested to be discussed in a coming weekly Developers Meeting.

New issue that just got created -- flag it so it can be reviewed/follow-up defined by maintainers

[Progress captain: assignee & maintainer] MR ready to be merged. Assignee should tag maintainers. Next state: Merged or "4. Change requested".

[Progress captain: assignee] Reviewer's comments need to be addressed (comments/code/test/docs/etc.). Conflict with target branch should be addressed carefully. Next state: "2. Review me!".