Skip to content

Community participation in issue triaging #56883

Closed
@chrmarti

Description

#34432 (comment)

There are several approaches, this issue is for discussing and adding to these.

@V-ed suggests having a way for the community to flag an issue as a duplicate of another, but not immediately close it. Instead the bot would label the issue community-triaged and after a few days close it.

Another approach would be to immediately close the issue (e.g., duplicates, questions) and add a label community-triaged, so the team could still query for these issues, but they also immediate disappear from our regular queries.

The bot could also label new issues by new reporters as first-issue (and post a welcome message) to help spot returning reporters. We could then think about weaving that into the community triage, but generally I prefer to go with less rules/process.

Metadata

Assignees

Labels

engineeringVS Code - Build / issue tracking / etc.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions