-
Notifications
You must be signed in to change notification settings - Fork 229
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
Identifying Causes of Backlog of old issues #1756
Comments
On #1658 I am collecting the list of emails and should be able to do it on Monday. I was planning on earlier, as other tech tickets I have, but ... work, and emails on Friday don't have the same reception. |
#1587 was fixed by a PR - but we forgot to close the issue. I closed it. |
I've renamed this ticket to be about 'identifying causes' rather than 'clearing' these tickets. This lets us better understand the sticking points and possible solutions, whether that's forgetting to close a ticket, or having too much one one's plate. |
All tickets seem to be moving along, I'll recheck today after our meeting |
It seems like we've been able to learn a few things @mariajoafana that helps us better understand some of the challenges people face closing tickets. In addition to your support and suggestions to reduce roles to 2, and possibly to bring in help for diagnosing or assessing bugs, is there anything else we want to know or explore? Or should we close this ticket? |
Closing this conversation so we can move ahead with supporting solutions |
We've had a gradual buildup of old issues getting stuck for a wide range of reasons. This is a new problem that is worse than we've experienced so far. In order to make sure it doesn't become endemic, I'm opening this ticket and asking our Project Manager at Large @mariajoafana to help identify causes and also to help people responsible for the tickets to action them and complete the tasks or otherwise ask for the help they need in order to do so.
Some of these are active. Others are not.
Please don't regard this as a scolding of any kind, but I would value understanding the reasons some tickets linger and others do not. If it's a matter of not understanding who is responsible for tasks, or forgetting, or not being interested in the task, we really need to know so we can make sure we run efficiently. Thanks everyone.
The text was updated successfully, but these errors were encountered: