-
Notifications
You must be signed in to change notification settings - Fork 210
Description
Describe the bug
We currently mark issues as stale after 30 days and automatically close them 14 days later:
days-before-issue-stale: 30
days-before-issue-close: 14This workflow assumes issues are tracked externally (for example, in JIRA), but we are not using JIRA or any other system to track active issues. As a result, user-reported issues that are still valid but have not received recent activity can be automatically marked stale and closed within ~45 days, even though they may not have been triaged or resolved. This risks losing legitimate issues and negatively impacts visibility into active issues.
To Reproduce
N/A
Expected behavior
We should look into disabling the stale issues similar to how Gluten does it today as it also does not use JIRA to track active issues.
Screenshots
Additional context