Jquery-validation: Unresolved issue reports automatically closed by stale bot

Created on 8 Oct 2018 · 6Comments · Source: jquery-validation/jquery-validation

I reported issue #1694 in 2016. In August, the ticket was automatically closed by a bot with as only reason that there hadn't been any activity on the ticket in 60 days, even though it is not specified what activity could help besides resolution.

I don't mind people asking me if a bug I reported 10 years ago persists. I also don't mind someone closing a ticket saying "hey, I'm not sure this is solved, but this hasn't been reported in 15 years and I didn't see this bug in years of usage, so I'm going to assume it's been fixed and close". But automated closure of a perfectly reproducible and easily verifiable issue after 2 months is a different story.

Is this representative of how this project intends to manage quality?

P.S. I understand some may consider that this ticket does not report an issue and meant to discuss this in a forum, but opened a ticket instead since there is no forum currently.

Source

Chealer

Most helpful comment

Could you please disable the bot for now?

done.

staabm on 14 Oct 2018

👍2

All 6 comments

Hi @Chealer

thx for getting into this discussion.

the team of volunteers working on jquery-validation is very small and our free time, in which we work on this project - besides ours regular jobs - is rather limited.

If the mentioned issue is a problem for you, feel free to invest your free time and provide a pull request or a different solution which works for you.
It seems you are the only person having this issue (noone else involed in the issue thread) and it is not a priority for one of the core contributors.

please keep in mind this is a project which is not sponsored by anyone and everyone working on it is doing so in its free time for no money. this is how most open source projects work.

we use the bot to make sure we can manage the reported issues in the most effiecient way. a closed issue also doesnt mean noone care about it, but just that noone is able to spent time on it. if someone is able to solve it with a decent solution which fits into the projects this is fine.

please dont see this as some kind of offense against you. we really appreciate your feedback.

staabm on 9 Oct 2018

👍1

Hi @staabm ,
I fail to see how lack of sponsoring is related to automated closure of issue reports.
I don't know how the bot helps manage the reported issues in the most efficient way, but this is not against the bot - this is about its automated closure of tickets when there is no indication of resolution.

Closing a ticket does not mean that no one is able to spend time on the problem reported, it means that the problem was solved. If anything means that no one is able to spend time on a problem, that would in fact be... leaving the ticket open.

Chealer on 13 Oct 2018

HI @Chealer,

Thanks a lot for opening this issue. As we already said in #2198 and as @staabm said above, we are only volunteers and we don't always have the time to work on this repository. The number of issues we had before (some issues were opened in 2013) was overwhelming for us, and a lot of them didn't receive the attention they deserve, so closing them as can't fix is the best we have for now.

I agree with your sentiment about the automated closure of issues, but it was the best we can do to not give people the false hope that it will be fixed in the near future. I guess for now, we have a reasonable number of issues that we can work on, so I guess we will have to disable the bot.

Thanks a lot for your feedback :)