> On May 1, 2026, at 10:29 AM, Mads Toftum <[email protected]> wrote:
>
> On Fri, May 01, 2026 at 10:05:15AM -0400, Rich Bowen wrote:
>>
>>
>>> On May 1, 2026, at 9:33 AM, Mads Toftum <[email protected]> wrote:
>>> Would be tempting to close out old reports to get rid of some of the
>>> noise. If not by date, then at least close anything on unsupported
>>> versions.
>>
>> Yes, that would be fantastic. I’m never a big fan of bulk-closing tickets
>> based on age, but there’s *definitely* a lot of stuff in here against
>> modules that are long-retired, features that no longer exist, and a lot of
>> other ancient history.
>>
> I was thinking more along the lines of 1.3, 2.0 and 2.2 if there's any
> left from those versions.
Oh, yeah, those are all gone.
>>
>> Yeah, there’s a lot of user support stuff in here that isn’t actually a bug
>> report. There’s also a lot of tickets where someone did the work, fixed a
>> problem, and asked the reporter for their +1 to close, and then it just sat
>> and rotted. This kind of stuff is what the AI tools are actually good at,
>> and I’m going to do some more digging.
>>
> Perhaps an approach could be to have AI make suggested responses and
> then put a human in the loop before sending?
That is my planned approach. I am very reluctant to give any AI agent direct
access to the bz API or anything like that, but am trying to see how much I can
at least get recommendations on to close stuff.
—
Rich Bowen
[email protected]
