-
Notifications
You must be signed in to change notification settings - Fork 28
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
add an UI element to indicate taken/free issues #148
Comments
The task is not supposed to be visible if it's taken. Perhaps this feature is broken now? Maybe this approach does make sense for the ability to see every task in the network, but then to be able to further sort for availability. These days I even use the UI to quickly find some issue I was thinking about (it's way faster than any official GitHub UI for this purpose) so it could be nice to see regardless of its assigned status. |
It's broken, but yes, I imagine the DevPool as an important tooling not only for contributors finding an issue to tackle, but also for code owners to manage/view it all. Therefore I believe this is a nice feature to have. We should find the old broken code and remove it too. |
It's related to the |
A big advantage of scouting issues on GitHub instead of the directory is that we can't differentiate between taken and open issues. GitHub solves that by displaying the assignee's PFP:
We should add a UI element to differentiate between issues with an assignee and issues without one, also allowing to filter by the presence or absence of assignee. This should be very easy to do given that the issue object has the following structure:
An instance as example:
The text was updated successfully, but these errors were encountered: