You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This feature entails implementing an automated system to close old issues within the project management platform. It aims to declutter the issue tracker by automatically closing issues that have remained unresolved or inactive for a specified period. The system will identify these old issues based on predefined criteria and initiate the closure process accordingly.
Describe the solution you'd like
I envision a system that periodically scans the issue tracker for issues that meet the criteria for closure, such as being inactive for a certain duration or lacking recent updates. Once identified, the system will automatically close these old issues, providing a notification to relevant stakeholders if necessary. Additionally, the system should allow for customization of closure criteria to accommodate the specific needs of different projects.
Describe alternatives you've considered
One alternative approach could be manual closure of old issues by project administrators or team members. However, this method is time-consuming and prone to oversight, especially in projects with large issue backlogs. Another option could be archiving old issues instead of closing them, preserving their historical record while removing them from the active issue tracker. However, this may still result in a cluttered and less manageable issue tracker over time.
Add ScreenShots
NA
Record
I agree to follow this project's Code of Conduct
I'm a GSSOC'24 contributor
I want to work on this issue
The text was updated successfully, but these errors were encountered:
Describe the feature
This feature entails implementing an automated system to close old issues within the project management platform. It aims to declutter the issue tracker by automatically closing issues that have remained unresolved or inactive for a specified period. The system will identify these old issues based on predefined criteria and initiate the closure process accordingly.
Describe the solution you'd like
I envision a system that periodically scans the issue tracker for issues that meet the criteria for closure, such as being inactive for a certain duration or lacking recent updates. Once identified, the system will automatically close these old issues, providing a notification to relevant stakeholders if necessary. Additionally, the system should allow for customization of closure criteria to accommodate the specific needs of different projects.
Describe alternatives you've considered
One alternative approach could be manual closure of old issues by project administrators or team members. However, this method is time-consuming and prone to oversight, especially in projects with large issue backlogs. Another option could be archiving old issues instead of closing them, preserving their historical record while removing them from the active issue tracker. However, this may still result in a cluttered and less manageable issue tracker over time.
Add ScreenShots
NA
Record
The text was updated successfully, but these errors were encountered: