Closing issues because they are unplanned is bad UX

Author's image
Tamás Sallai
3 mins
Photo by Aaron Burden on Unsplash

Many projects close issues after a triage if the feature/bug is not planned. For example, the terraform-provider-aws uses a bot that detects stale issues (for example, I'm following this one and I'm getting periodic emails about it). If nobody comments for a period of time the issue gets closed.

I get why it's good for the project's perspective: if you open the issue tracker and it's full of open issues then it's both depressing and counterproductive as it buries the important things to work on. Most of these projects with a public issue tracker are open-source ones and the maintainers are usually not paid for their work. So it's not up to me to decide how they organize their work.

But from my side this pattern is a problem.

Let's say I encounter an edge case. I report it, find some workaround, and add a comment along the lines of "workaround for X, see ticket Y". But maybe it's outside the current priorities of the project so it gets closed. I get an email saying it's closed because it's "not planned".

Fast-forward a couple of years. Maybe then the issue is in-scope now for the project and they actually implement it. How do I know? I get notifications for the original ticket which was closed after opening it. And when something is closed, nobody goes back to it to let me know that now it's done. Maybe there is another ticket opened for the same thing, but I'm not subscribed to that one. I need to actively look for the fix to find it.

The same thing happens in internal projects as well. The backlog is always too large, so there is a tendency to say: we're unlikely to work on most of these things, so let's close the majority of these tickets.

My argument against this: even though these tickets are not useful now they can be useful in the future. Maybe someone will take a look at the backlog at some point and realize that some important thing did not get implemented. Or someone bumps into an issue and realizes that it's a known bug.

In this case the backlog is a list of things we know we don't have. Adding some tags so that they can be easily hidden would be a better solution.

December 15, 2025

Free PDF guide

Sign up to our newsletter and download the "How Cognito User Pools work" guide.