You must log in or register to comment.
Most counterproductive bug tracker feature ever.
I don’t think so. It should have an easy way of reopening - if it has, and you’re flooded with tickets on an open source project that you can’t possibly handle all, then it’s a good way to prioritize. Of course it doesn’t have an easy way to reopen here, which sucks, it’s some kind of locking instead of just closing it with a possibility to reopen.
Old tickets have a non-zero chance of the reporter being the only one to run into it because of a weird setup/usecase (and then abandoning the project), it being fixed by other work, or probably a bunch of other reasons it could be obsolete.
If no one cares enough to reopen it once every 6 months, then it’s probably fine to ignore it indefinitely.
“Locked” implies no easy way of reopening.
I understand that developers don’t always have time or interest to fix my problems (specially with FOSS projects), but this just feels like rubbing it in my face. Just close the issue after initial assessment if it looks like a non-fixable and low priority.
“See this is how much we care, we even have a bot to remind you that we are still ignoring you”
exactly, if devs ignore issues that is to me just them telling the world that they don’t care about the project and we should encourage people to fork it and take over the mantle of de-facto version, or just let it die if it’s not important.
This except it’s activity on the PR I submitted and it’s just a bot marking it as stale because there’s been no activity. Well it’s ready to merge if a maintainer would just click the button… Or tell me why they won’t merge it
every time I see this it always follows with comment that reopens the issue. inactive != resolved.
