robertfmurdock / coupling Goto Github PK

Ability to form mobs or multi-mobs.

Scenarios:

1) A team pairs but also sometimes mobs together, so you end up with a mix. You might have more of a mix: some pairs and maybe a mob or two on a given team
2) A team always mobs or splits into multi-mobs

Example: Right now I work on a team where half the time we are working in 3s not just 2s. The ability to drag someone over and make a current pair a mob would be super useful for the history and visibility and would more realistically match how we work on this given team

I imagine that if we had such a thing, it would rewrite history (it'd create a new entry in the History for the creation of a mob after a spin has already been saved). That way we could record newly formed mobs and have it somehow be accounted for in the pair algorithm / heat map?

Adding this feature would require (so separate stories for these):

• Ability to drag/persist more than 2 people into a pairing group/assignment
• Spin is able to take into account groups that have more than 2 people to determine rotations
• History is able to account for groups that have more than 2 people
• Heat map is also able to take into account stats based on your time mobbing with certain people
• UI would need to flex as group participants increase (resize them appropriately) to show more than 2 people. You could add a third card say on top of a pair, but what if you have more than 3 in a mob? resizing groups would need to happen so that you can view the pairing group/assignment better
• Put a limit on how many can be in a group? Maybe limit to 6?

Steps to reproduce:

1. Add a new player and leave the name field empty
2. Hit Save Button

Observed:

• Unable to select player for editing in the UI
• After navigating to player's edit screen directly, saved changes were not applied

Add some information that tells the user that the automatic prioritization is left to right... the farthest pair to the left is the highest prioritized pair, the farthest to the right is the lowest priority.

Make the report issue button link to the github issues area.

When a brand new person joins the team, the pairing algorithm should prioritize making pairs for old/existing team members first because it doesn't matter who the new person is paired with.

All currently retired players should be visible on the Retirement page and be able to be restored to the team from there.

Description: I want an easy way to quickly bring up other resources while we determine pairing such as Story Board, etc.

Example links might be to a notion page, Jira (God forbid), OneNote, Trello Board, etc.

GIVEN I have a team Party
WHEN viewing my team's Party
THEN I see an area that allows me to show links in this Hub

Hub: a place where I can add a few hyperlinks to team resources that live outside Coupling.

Mockup:

When a user logs in, if their email is used by a player in a tribe, then that tribe is available to them.

Additionally, their user can be granted permission to use a tribe by having the tribeid given to them in an ‘authorized_tribes’ array. That’ll stay backendy for now.

In order to support non-gmail email addresses, add local authentication. Not having this feature seems to be a barrier to use for certain enterprise clients.

Two distinct but related thoughts:

• Make the "delete" buttons on the history page no longer actually remove data, but instead mark the record as "deleted" and have a timestamp of when the deletion occurred.
• Make the "spin" endpoint actually persist the generated pairings immediately. Could be in the history collection, could be somewhere else. The generated pairings should be ignored by the algorithm... only pairings that have been "saved" by a user should affect the algorithm. Lets also make the generated pairings know which user triggered the spin.

This way we can always tell what the system recommended, and then what the humans decided to go with.

So... upgrade the history page to be able to indicate pairings that were user-modified, and be able to show the recommendation.

Currently tribes can only get unique images via a workaround. This is dumb. Fix it.

Repeatedly asked to sign in rather than being authenticated

Fix it.

I'd like to add a feature that automatically assigns 'pins' whenever the pairs are spun.

A 'pin' is defined as a special job that lasts for the duration of the iteration. For the first implementation, one person can have one role (having the option of creating a paired role would be a future feature).

I'd like the pin to be displayed as an overlay image on top of the player's card.

It looks like at least one user has experienced a bug where the algorithm kept producing the same set of pairings, even though it was saved in between each session.

Importing the tribe to a different instance of Coupling did not demonstrate the error for some reason.

Outstanding issue. Please report more information if you observe something similar.

Hi Rob,

It is sometimes necessary for different team (tribe) members to access the coupling app to generate coupling assignments. Passwords must not be shared among team members. It would be best for each person to login with their own credentials to access their tribe and spin for pairs. Is this currently supported?

Thanks!
Doug

Add some checkboxes that reveal some of the information related to pairings on the heat map itself. Such as:

• times paired in 'heat window'
• iterations since last pairing

Currently given a player permission via email will not work unless their email matches the case from the auth provider.

Make it work regardless of case.

Allow a tribe to opt to use the badge group system. This will:

• Allow the user to enable / disable the badges
• Allow the user to name two distinct badges, a default badge and an alternative badge
• Allow the user to choose the badge each player should have, defaulting to the default badge.

Allow the user to choose a badge group rule that will affect the pairing algorithm. For this issue, allow 'none' and 'prefer different badge' to be the rules.

If I fail to put in all required tribe information, a new tribe will not be created, I am navigated to a different screen, and no error message is displayed. It is unclear what fields are required, so I don't know what to fix or even what went wrong.

Desired behavior: When I navigate to the tribe creation screen, I can identify which fields are required. When I fail to give all required tribe information, I stay on the same screen and receive an error message detailing why creating the tribe failed.

Self explanatory I think.

Show a page that will include a few basic stats about the team, including:

• Number of iterations it will take to complete a 'full rotation' with all players
• Same, but only with players who participated in the last spin
• All of the possible pairs, ordered by longest time since they occurred to recent, so a user can see pairs that haven't occurred recently.

Can the UI display some kind of key for the color map? Or add the statistics to the cell?