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

[Feature] Please improve auto-closing of issues #3474

Open
marcindulak opened this issue Feb 13, 2023 · 22 comments · May be fixed by #4611
Open

[Feature] Please improve auto-closing of issues #3474

marcindulak opened this issue Feb 13, 2023 · 22 comments · May be fixed by #4611
Labels
feature-request Requested Features

Comments

@marcindulak
Copy link

Is your feature request related to a problem? Please describe.

An issue #3381 which appears to be valid, was closed without triage, due to inactivity.

Describe the solution you'd like

The solution may get an inspiration from kubernetes/kubernetes#103151, but at a minimum the issues that were not reviewed by a human should not be auto-closed.

Copy link
Contributor

Action required from @Azure/aks-pm

@microsoft-github-policy-service microsoft-github-policy-service bot added the Needs Attention 👋 Issues needs attention/assignee/owner label Feb 8, 2024
Copy link
Contributor

Issue needing attention of @Azure/aks-leads

16 similar comments
Copy link
Contributor

Issue needing attention of @Azure/aks-leads

Copy link
Contributor

Issue needing attention of @Azure/aks-leads

Copy link
Contributor

Issue needing attention of @Azure/aks-leads

Copy link
Contributor

Issue needing attention of @Azure/aks-leads

Copy link
Contributor

Issue needing attention of @Azure/aks-leads

Copy link
Contributor

Issue needing attention of @Azure/aks-leads

Copy link
Contributor

Issue needing attention of @Azure/aks-leads

Copy link
Contributor

Issue needing attention of @Azure/aks-leads

Copy link
Contributor

Issue needing attention of @Azure/aks-leads

Copy link
Contributor

Issue needing attention of @Azure/aks-leads

Copy link
Contributor

Issue needing attention of @Azure/aks-leads

Copy link
Contributor

Issue needing attention of @Azure/aks-leads

Copy link
Contributor

Issue needing attention of @Azure/aks-leads

Copy link
Contributor

Issue needing attention of @Azure/aks-leads

Copy link
Contributor

Issue needing attention of @Azure/aks-leads

Copy link
Contributor

Issue needing attention of @Azure/aks-leads

@sjwaight
Copy link
Contributor

This looks like it's been addressed. If you feel that's not the case @marcindulak please feel free to reopen.

@marcindulak
Copy link
Author

Unfortunately I don't have permissions to reopen the issue, which is surprising since I'm the issue reporter.

@sjwaight Could you provide some details how the handling of auto-closed issues was improved?

Please note that 4 days ago an issue on the roadmap got auto-closed by the bot #2125 (comment)

@sjwaight
Copy link
Contributor

Reopening as it's not addressed. Thanks for sharing a recent example @marcindulak. I'll take a look at the sample and see why the bot undertook the action it did.

@sjwaight sjwaight reopened this Oct 28, 2024
@microsoft-github-policy-service microsoft-github-policy-service bot removed action-required Needs Attention 👋 Issues needs attention/assignee/owner labels Oct 28, 2024
@sjwaight
Copy link
Contributor

sjwaight commented Oct 29, 2024

This appears to be due to config ignoring items that hold the 'Under investigation' label OR that are a part of a project. The second item appears to be due to the recent changes to GitHub Projects. I'm tracking this and will update once I have an answer.

@marcindulak I see you have a range of other issues that you have tagged prior to closing across a bunch of other areas. To help aid us in managing a noisy repo it would be good to let issues be closed by the bot until we've had a chance to fix this issue.

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

Successfully merging a pull request may close this issue.

2 participants