Would this be a one-time action or something regular? As in, would an option in the settings be enough or would we want some sort of cron or automated feature?

I kinda lean on the first one as it would a) allow to review tickets before closing them and b) would most likely be easier to implement :D

The feature I would like to see once it comes to auto-close is: I would like to set per ticket, that if nobody changes the ticket (no new comment, nothing) within n days, close the ticket with a configurable reason and a configurable comment. So something like a very basic workflow.

Something like that should be considered for 6.0, it would definitely help to reduce the open issues without updates.

Something like that should be considered for 6.0, it would definitely help to reduce the open issues without updates.

That's always a tricky subject: the fact that nobody worked on something for a
year doesn't make the issue invalid per say. It could still be a valid bug or
RFE that has just not been prioritized.

That being said, we could still implement this on a per project configuration
with a daily cron job or alike

Agree, my feeling is that all these improvements should be something that can be enabled and used, but probably should be off by default to leave the behavior similar as it's today. For obvious reasons I found this Idea very attractive when I started to work through the backlog yesterday ;)