Group Voting

EstimateQuest supports group voting — assigning tickets to specific teams so only relevant voters participate in each estimation.

How Groups Work

Each voter selects a group when joining the session:

Group	Color
Frontend	Blue
Backend	Green
Mobile	Purple
QA	Orange

Each ticket is assigned to one or more of these groups. When a ticket comes up for voting, only voters in the assigned groups see their estimation cards and can cast votes.

Single-Group Tickets

If a ticket is assigned to just one group (e.g., Frontend only):

• Only Frontend voters can vote
• Backend, Mobile, and QA voters see a “not your turn” state
• The final estimate applies to that single group

Multi-Group Tickets

If a ticket is assigned to multiple groups (e.g., Frontend + Backend):

• Voters from both groups can vote simultaneously
• After reveal, votes are shown grouped by team
• The moderator sets a separate estimate for each group
• A final overall estimate can also be set

This is useful for full-stack features where frontend and backend effort may differ significantly.

All-Group Tickets

Assign all four groups when the entire team should estimate together. All voters participate and the moderator can set per-group estimates or a single overall estimate.

When to use group voting

Group voting shines when your team has specialists. A frontend-only bug doesn’t need backend input, and a database migration doesn’t need frontend votes. Assign groups thoughtfully to keep estimation sessions focused and efficient.

Group Badges

In the Player Arena, each voter has a colored badge showing their group. This makes it easy to see the team composition at a glance and understand whose votes are being collected for each ticket.