Iteration 2: org > repo (scenario: free plan / no more members)

[codecovdesign]

Problem to solve

Context: in this iteration #1253 we updated the scenario where users were hitting an error state when attempting to configure a repo; due to org being on a free plan and not having any more seats.

In this iteration, we are focused on the scenario that a repo is configured and user still sees the error page. Today, it's not explicit as to why the error is showing. The user could benefit from understanding the plan rules of 1< have been exceeded in addition to path forward for plan upgrade.

Solution

• WHEN user navigating to configured repo and IF the org is free OR seats unavailable show explicit UI to what the issue is
  • IF free plan => anchor to org > plan
  • IF paid => anchor to org > member

view designs

Free plan, no seats	paid plan, but no more seats	paid plan, and seats are available

Tasks

Preview Give feedback

1. [Gazebo] Display a new error on the repo page for PAID plans when all seats are taken #1316
   1 of 1
   +0
   
2. [Gazebo] Display a new error in the repo page for FREE plans when all seats are taken #1317
   1 of 1
   +0
   
3. [API] Add a new hasSeatsLeft field to plan query #1318
   +0
   
4. [Gazebo] Display a new error on the repo page for PAID plans when there are seats available and current user is not activated #1346
   1 of 1
   +0
   

[codecovdesign]

• update scope to include scenario where user is on paid plan and a seat is available ✅
• future iteration to look at clarifying plan management and what "activation" and "seats" mean