I often go spelunking in JIRA and find old tickets that are hard to validate, or, if I ping the creator, they have long moved on and can't share any more details.
What do you think about using the same labels as in in our PRs? You could imagine that sixty days after a JIRA being opened we add "stale" and then 60 days after that "closed-stale". I would be fine with any activity counting as a reset. For your Tier 1, you could do "housekeeping-2026" and "closed-stale". If we committed to doing this, I would be happy to dig into the Tier 2 and Tier 3 lists. Eric On 2026/06/10 08:13:25 Jason Gerlowski wrote: > > I know there are different philosofies on such gardening. Some hate it, > > some love it, some don't care. > > I think I'm in the "don't care" category. Or at least, I'm not sure > how to feel about it. I tend to use JIRA to track my own work or read > about what others have been working on recently (via the mailing > list). I haven't seen "noise" being a big problem there, but I'm open > to folks having different usage patterns where there is more negative > impact. Was just fishing for a concrete example I guess :-p. I > appreciate the addtl detail! > > Consider me a +0. Agree with David's comment that it'd be great to > find an appropriate Resolution that'd make the "auto-closed for > staleness" easy to detect down the road. > > Best, > > Jason > > > On Fri, Jun 5, 2026 at 9:45 PM Jan Høydahl <[email protected]> wrote: > > > > Hi, > > > > 8.5 years mean age. You can pick a random open JIRA issue for Solr and most > > likely you'll find that it is not open at all, it is something that is > > either not relevant anymore, fixed somewhere else or just an idea that > > stalled 5 years ago and is superceded by something else. > > > > Whether it is a problem depends on what you expect from an issue tracker > > and what you expect from a "state" field. > > Some might not care at all, and that's ok. I think this much cruft is a > > noise issue. And it is easy to deal with. > > I call it gardening. > > > > If we did not have stalebot for PRs, I'm sure there would have been 2000 > > open PRs instad of the current 281... I have been reminded a few times by > > the bot that I had some work that started to go stale, and I'm triggered to > > either bring it to completion or close it. I want to do the same with > > Github Issues once we (perhaps) migrate away from JIRA. > > > > I know there are different philosofies on such gardening. Some hate it, > > some love it, some don't care. > > > > Jan > > > > > 5. juni 2026 kl. 21:30 skrev Jason Gerlowski <[email protected]>: > > > > > > You mention the existing situation being untenable - can you expand on > > > that a bit please? Are the old, untouched JIRAs causing some sort of > > > problem? > > > > > > Best, > > > > > > Jason > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [email protected] > > > For additional commands, e-mail: [email protected] > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
