-
-
Notifications
You must be signed in to change notification settings - Fork 777
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
Lead Dashboard: Dev #4294
Comments
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
Full reportDev Dashboard 2023-03-26 Good First Issue front end & back end Good Second Issue front end & back end Small backend Small front end Medium backend Medium front end Large backend Large front end |
Summary of PrioritiesDev Dashboard 2023-03-26 1️⃣ The new front end team members that have finished their good first issue and are ready to start on their second issue will be stalled after the second issue. Because we have just enough for the people already waiting below and there are potentially 9 people who are going to finish their second issue in the next week Small front end Small backend
2️⃣ We have 9 people who need good second issues and only a total of 8 issues between good first and good second. And we have an onboarding scheduled for Tuesday. So we probably need at least a total of 30 good first and second issues (15 good first issues would be a good start) Good First Issue front end & back end
Good Second Issue front end & back end
3️⃣ We are just a little bit short of issues in prioritized backlog for the people queuing Medium front end
4️⃣ We are just a little bit short of issues in prioritized backlog for the people queuing Medium backend
5️⃣ We are likely to need more Large frontend issues soon based on the 4 people doing medium issues now who are front end only. Large front end Large backend
|
Issues to close if no responseIssues to close 30-30
Issues to close 04-02
Responded, check on them in a few days
At message them with the following
|
|
Full reportDev Dashboard 2023-04-06 Good First Issue front end & back end Good Second Issue front end & back end Small backend Small front end Medium backend Medium front end Large backend Large front end |
This comment was marked as outdated.
This comment was marked as outdated.
Good First Issue front end & back end Small backend Small front end Medium backend Medium front end Large backend Large front end |
Please add update using the below template (even if you have a pull request). Afterwards, remove the 'To Update !' label and add the 'Status: Updated' label.
If you need help, be sure to either: 1) place your issue in the developer meeting discussion column and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel. Please note that including your questions in the issue comments- along with screenshots, if applicable- will help us to help you. Here and here are examples of well-formed questions. You are receiving this comment because your last comment was before Tuesday, May 30, 2023 at 12:15 AM PST. |
Please add update using the below template (even if you have a pull request). Afterwards, remove the '2 weeks inactive' label and add the 'Status: Updated' label.
If you need help, be sure to either: 1) place your issue in the developer meeting discussion column and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel. Please note that including your questions in the issue comments- along with screenshots, if applicable- will help us to help you. Here and here are examples of well-formed questions. You are receiving this comment because your last comment was before Tuesday, June 6, 2023 at 12:16 AM PST. |
Hi @anjolaaoluwa please leave an update on this issue. Thank you. |
Please add update using the below template (even if you have a pull request). Afterwards, remove the '2 weeks inactive' label and add the 'Status: Updated' label.
If you need help, be sure to either: 1) place your issue in the developer meeting discussion column and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel. Please note that including your questions in the issue comments- along with screenshots, if applicable- will help us to help you. Here and here are examples of well-formed questions. You are receiving this comment because your last comment was before Tuesday, June 13, 2023 at 12:16 AM PST. |
Why did we close the issue? |
@ExperimentsInHonesty This is fantastic work and it will be very valuable to dev leads, but I noticed that when I select "front end only", the Prioritized Backlog column does not appear. I checked the Project Board and in fact there are no "front end only" issues in the Prioritized Backlog column, but it might be better if the Prioritized Backlog column was displayed even if the number of issues is zero. |
@roslynwythe please walk us through that when we see you later today. |
@roslynwythe can you check this when the dashboard is working again. #6229 |
Dependency
Overview
We need to create a dashboard so that it is easy for Dev Leads to know where to focus their effort to maintain a healthy backlog of issues for each complexity type while addressing time sensitive requirements.
Action Items
Template
Resources/Instructions
The text was updated successfully, but these errors were encountered: