Currently, short-lived branches and PRs are red (failing) if there are any issues in a status other than Resolved or Closed. This means that every issue must either be fixed, or marked as FP / WF. But there will always be a few issues here and there, such as those raised on "ToDo" comments, that we simply need to Confirm and move on with. Further, we need that Confirmed status to be propagated to downstream instances (PR's, long-lived branches).
We will move a branch or PR to green (passing) when there are no status=Open issues. Specifically, if all issues have been Confirmed or marked FP/WF, the status will move to passed/green/mergable.
At the same time, we must not lose sight in the interface of non-Closed issues (Open, Confirmed, Resolved). This will be obvious on the short-lived branch landing page - Issues - but could be overlooked on the Code page of a short-lived branch or PR, and might be missed entirely in a project's list of branches.
The branch dropdown displays the green dot even though there are remaining issues.
When selecting this branch for investigation, the user can see a "?" helper. It displays an explanation on mouse-over.
When the quality gate changes, webhooks should be triggered.