-
Notifications
You must be signed in to change notification settings - Fork 156
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
Track inactive claimed issues (ODK bot) #298
Comments
I totally agree with @Divya063. Most of the issues have been inactive for more than a week. |
According to https://github.com/opendatakit/zulipbot/blob/master/src/config.js#L34 the bot should remind claimers after 7 days if they haven't worked on an issue. And then if there is no action on the issue, it removes the claim 3 days later (so a total of 10 days to work on an issue). Here is an example of it working: getodk/collect#170 (comment). Is there a claimed issue where you've seen this process not working? |
Well, we've filed the issue upstream, so that's all we can do at this time. We can't trust the bot to do everything 😂. I propose we close this issue, and as a stop-gap, @adammichaelwood (on this repo) and @lognaturel (on the other repos) occasionally sweep the issues to find stale issues. @adammichaelwood, if you agree, please close this issue. |
I agree. |
Fixed by getodk/zulipbot@6ae9dbd |
Feature:
If a claimed issue has not been updated for a week, @opendatakit-bot should post a comment on the inactive issue to ask the assignee if they are still working on the issue.Assignee should reply to the comment to notify the bot that he/she is still working on it.If the bot does not receive a response from the assignee within certain number of days it should automatically remove the issue's current assignee(s) and the "in progress" label to allow others to work on an inactive issue.
The text was updated successfully, but these errors were encountered: