Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[CAL-3100] Round Robin Fairness Algorithm #13606

Open
CarinaWolli opened this issue Feb 8, 2024 · 2 comments
Open

[CAL-3100] Round Robin Fairness Algorithm #13606

CarinaWolli opened this issue Feb 8, 2024 · 2 comments
Assignees
Labels
consumer ✨ feature New feature or request Medium priority Created by Linear-GitHub Sync teams area: teams, round robin, collective, managed event-types

Comments

@CarinaWolli
Copy link
Member

Stop assigning to a user when a given fairness threshold is reached, even if this person is the only possible assignee, if it is determined unfair we disable this user.

Example:
If a round-robin host is assigned to more than 5 bookings more than the other round-robin hosts, their availability won't be shown and they can't be booked.

Things to consider:

  • This will make debugging availability issues more complex, we should think about adding something to help debug missing slots disabled because of fairness.
  • How to deal with newly added hosts: If a host is getting added when other hosts already have a lot of bookings the new host can be booked many times until they reach this amount of bookings. This is not ideal and should be handled differently

From SyncLinear.com | CAL-3100

@CarinaWolli CarinaWolli added consumer Medium priority Created by Linear-GitHub Sync teams area: teams, round robin, collective, managed event-types ✨ feature New feature or request labels Feb 8, 2024
@maige-app maige-app bot added the 🚨 needs approval This feature request has not been reviewed yet by the Product Team and needs approval beforehand label Feb 8, 2024
@CarinaWolli CarinaWolli removed the 🚨 needs approval This feature request has not been reviewed yet by the Product Team and needs approval beforehand label Feb 8, 2024
@keithwillcode keithwillcode added this to the v3.9 milestone Feb 8, 2024
@CarinaWolli CarinaWolli modified the milestones: v3.9, v4.0 Mar 5, 2024
@keithwillcode keithwillcode modified the milestones: v4.0, v4.1 Apr 15, 2024
@CarinaWolli CarinaWolli modified the milestones: v4.1, v4.2 Apr 16, 2024
@CarinaWolli CarinaWolli modified the milestones: v4.2, v4.3 May 16, 2024
@CarinaWolli CarinaWolli modified the milestones: v4.3, v4.4 Jun 3, 2024
@CarinaWolli CarinaWolli self-assigned this Jun 5, 2024
@joeauyeung
Copy link
Contributor

joeauyeung commented Jun 5, 2024

@CarinaWolli to ensure that we're meeting the requirements found in this doc

@CarinaWolli CarinaWolli modified the milestones: v4.4, v4.2 Jun 5, 2024
@CarinaWolli
Copy link
Member Author

CarinaWolli commented Jun 5, 2024

@CarinaWolli to ensure that we're meeting the requirements found in this doc

I think this is what we want instead: #15340

@CarinaWolli CarinaWolli removed this from the v4.2 milestone Jun 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
consumer ✨ feature New feature or request Medium priority Created by Linear-GitHub Sync teams area: teams, round robin, collective, managed event-types
Projects
None yet
Development

No branches or pull requests

3 participants