Skip to content
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

[ENHANCEMENT] Improve untriaged label workflow to ignore issues created by maintainers #157

Open
joshuarrrr opened this issue Apr 20, 2023 · 4 comments
Labels
enhancement New feature or request

Comments

@joshuarrrr
Copy link
Member

Is your feature request related to a problem?

We use the untriaged workflow to add the untriaged label to all new issues, as described in #133

This is a good mechanism to ensure each repository has the right processes in place to routinely triage issues, where the label is manually removed. It also supports accountability, because we can simply check for untriaged issues that have had that label for some time.

But this does add unnecessary overhead to maintainers, who often create the majority of all issues in a repository, particularly when breaking down large epics or initiatives into subtasks. This can lean to temporary spikes in the untriaged metrics until the newly created issues are manually cleaned up.

What solution would you like?

By definition, a triaged issue is one which maintainers have deemed valid. So the untriaged workflow should simply skip any issues created by maintainers. I'm not sure of the best programmatic way to access the maintainer list from within the workflow, but suspect that the newly baselined CODEOWNERS files will help.

What alternatives have you considered?

None so far.

Do you have any additional context?

Related to #102

@joshuarrrr joshuarrrr added enhancement New feature or request untriaged labels Apr 20, 2023
@dblock
Copy link
Member

dblock commented Apr 21, 2023

It would be amazing to turn the untriaged workflow into a proper GitHub app similar to DCO with features such as this one, so we don't have to configure a manual workflow in every repo.

@peternied
Copy link
Member

This can lean to temporary spikes in the untriaged metrics until the newly created issues are manually cleaned up.

Sounds like you are trying to 'game' the graph, could you provide more detail on where is that graph is and how your team acts on it?

For the repos I maintain there are no graphs that we monitor; we use GitHub queries during our weekly triage [1].

@ashwin-pc
Copy link
Member

Opensearch Dashboards has solved this issue like this. opensearch-project/OpenSearch-Dashboards#6193

@dblock
Copy link
Member

dblock commented Apr 6, 2024

We'd have to edit 100+ workflows :( It would be really great to have a bot that does this across the entire org.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

4 participants