On Thu, Oct 6, 2022 at 12:11 PM Antonin Delpeuch (lists)
> On 06/10/2022 16:57, Tom Morris wrote:
> > Note also that Github has a bulk edit facility, ...
> Amazing! How do you use this bulk edit facility? I never discovered it
> in the web UI - it does feel like something I would use often!
In the issue list view, any edits made using the header pulldowns act
on all selected issues. Clicking on the checkbox in the header will
select all issues on the current page. I'm not sure if there's a way
to do more than a page's worth. I ended up doing the 99 issues in four
separate chunks of 25.
> > I think there's value in having a well-groomed backlog and that the
> > triage process is a net value-add, but it's really up to the project
> > team to figure out what works best for them.
> Yes - so instead of deleting the tag we could we could encourage more
> people to chime in the triage, and I wonder how.
Two possible suggestions are to 1) ask team members to self-triage for
issues that they create (I just cleaned up all mine) and 2) ask for a
volunteer from the community to take point as the designated triager.
This is probably only an hour or two a week worth of work at the
current bug volumes. A prerequisite for this would be a description of
the desired triage process and/or post-triage state for issues.
For the historical backlog, here are some links for team members to
review their own issues:
> I think our tagging scheme is not so great and would be worth making a
> bit more consistent, or at least better documented. Perhaps that would
> make people more confident that they can make this call.
I agree. One thing worth considering would be whether adding more
prefixes like the current "Priority: " prefix to group like tags
together would be helpful. That would, for example, help all the
component/category tags collate together. Removing/combining obsolete
and/or low frequency usage tags could help make the tag set smaller
and easier to understand.