Work as a team
Team issues
Quality problems one team causes another, raised by a lead or by Rabbinatix, answered by the team they are against, and counted in each team’s health.
Open Team issues in the appWhat it is for
Team issues are kept per project so teams improve rather than argue. An issue is against the team that owns the system and from the team it affected, or from Rabbinatix for automatic ones. At the top of Team issues, Team health shows every team side by side: issues raised against them in 30 days, open ones by severity, the median time to fix, how many were marked not valid, sign-offs answered late, and moves without sign-off.
Raised by Rabbinatix
Each automatic issue is raised once, with what caused it, and closes by itself when the cause is gone:
- a team promise broken;
- a move without sign-off from a team;
- a sign-off answered later than the team promised;
- a contract between two teams' systems that breaks, when the project turns this on in the team issues Settings (off by default). It closes when the contract works again.
Raise one
A team lead presses Raise a team issue, gives a title, what happened, the team it is against, optionally the system, and how serious it is: Low, Medium or High. Their leads are told.
Where else it shows
Type @ in chat, a ticket or a page to mention a team issue or a team promise; pasting a link to one shows a card. The command palette finds them by key or title, and Raise a team issue is one of its actions. On the dashboard, who acts for a team sees what waits for their team, this week's planned releases and who is away, and their teams' health.
Answer one
The team it is against presses Acknowledge to say they've seen it, then Fixed with what fixed it. The team that raised it can Reopen it with a reason. Create ticket makes a ticket on the board linked to the issue; the issue doesn't close when the ticket does.
Mark not valid
After the leads talk, the team it is against can press Mark not valid with the reason ("agreed in the call on 12 Nov: the field was never documented"):
- with approvers picked (optional), it waits for them, with the same rules as approvals of moves: any one, all, or at least some. One refusal keeps it open, and the closed issue says Approved by …;
- with nobody picked, it is marked at once and the other team may reopen it within 14 days. Where the team issues settings Ask for approval first, the issue then says Without approval: approvals never block, they record who shared the call.
How many issues a team marked not valid is shown in Team health, so marking everything not valid is visible.
What is kept
Open issues, and closed ones for 90 days; older ones are under Show older.
Related
- Team promisesWhat one team promises another for a system: uptime, response time, notice before breaking changes, how fast a service is fixed, how fast sign-offs are answered — agreed by both, measured by Rabbinatix.
- Sign-off from affected teamsWhen a release changes or breaks the calls other teams make, those teams are asked to sign off before it moves; every answer and every move without one is recorded.
- The board and ticketsTrack work as tickets on one board: types, columns, tags and sprints, mentions that open the exact place, and the planning views.
