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.

Sign up for GitHub

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

Jump to bottom

[Tooling] Automate closing issues that needs more info after a designated time period #11235

Open
DitwanP opened this issue Jan 8, 2025 · 0 comments
Open

[Tooling] Automate closing issues that needs more info after a designated time period #11235

DitwanP opened this issue Jan 8, 2025 · 0 comments
Assignees
@DitwanP
Labels
1 - assigned Issues that are assigned to a sprint and a team member. estimate - 3 A day or two of work, likely requires updates to tests. p - low Issue is non core or affecting less that 10% of people using the library tooling Issues relating to build system fixes or improvements.
Milestone
2025-02-25 - Feb ...

Comments

@DitwanP
Copy link
Contributor

DitwanP commented Jan 8, 2025

Priority impact

p - low

Summary

At times we are unable to reproduce issues and we do not receive additional info or repro example in a reasonable amount of time. In these cases we want to automatically close these issues with a message that lets the original poster know that they can reopen if the issue is still present and once additional info is provided.

We can use the needs more info label for creating the automation.

Desired Outcome

Issues with request for more info and needs more info label should automatically close after a designated time period without response.

Time frame should be around 1 or 2 weeks (TBD)

Resources

No response
@DitwanP DitwanP added tooling Issues relating to build system fixes or improvements. 0 - new New issues that need assignment. estimate - 3 A day or two of work, likely requires updates to tests. needs milestone Planning workflow - pending milestone assignment, has priority and/or estimate. labels Jan 8, 2025
@github-actions github-actions bot added the p - low Issue is non core or affecting less that 10% of people using the library label Jan 8, 2025
@DitwanP DitwanP added this to the 2025-02-25 - Feb Milestone milestone Jan 13, 2025
@DitwanP DitwanP removed the needs milestone Planning workflow - pending milestone assignment, has priority and/or estimate. label Jan 13, 2025
@DitwanP DitwanP self-assigned this Jan 13, 2025
@DitwanP DitwanP added 1 - assigned Issues that are assigned to a sprint and a team member. and removed 0 - new New issues that need assignment. labels Jan 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@DitwanP DitwanP

Labels
1 - assigned Issues that are assigned to a sprint and a team member. estimate - 3 A day or two of work, likely requires updates to tests. p - low Issue is non core or affecting less that 10% of people using the library tooling Issues relating to build system fixes or improvements.
Projects
None yet
Milestone
2025-02-25 - Feb Milestone
Development

No branches or pull requests
1 participant
@DitwanP