Turns out I switched it on in some projects but not all. I simply forgot about it.
I will rectify this during the next days. Please note that this will trigger quite a few warnings about upcoming closure and it would give Jason a limited window to resolve. Therefore this has to be in stages. Likely I will start with 2018 issues. -- Alex ________________________________________ From: Development <[email protected]> on behalf of Jason McDonald <[email protected]> Sent: Tuesday, 3 November 2020 04:36 To: development Subject: Re: [Development] Handling of Needs More Info issues in Jira On Tue, 3 Nov 2020 at 05:48, Oswald Buddenhagen <[email protected]<mailto:[email protected]>> wrote: On Mon, Nov 02, 2020 at 08:01:13AM -0800, Thiago Macieira wrote: >On Monday, 2 November 2020 05:24:45 PST Jason McDonald wrote: >> There may be such a tool, but if there is it presumably isn't functioning >> anymore (unless it's definition of "too long" is more than two years). > >I think it was supposed to be run manually every 6 months or so, closing >entries that were more than 3 months without interaction (or so). The "run >manually" might be the problem... > iirc, said tool was implemented as two (?) "cron jobs" running daily (?) entirely inside jira. the timeouts for the heads-up and subsequent closure were measured in weeks. alex' announcement is here: https://lists.qt-project.org/pipermail/interest/2018-August/030752.html dunno what went wrong ... Thanks Ossi. That's useful information (and I like the other changes mentioned there too). I will file a bug in the QTJIRA project asking for those cronjobs to be reinstated and a human to be notified if they break again. Cheers, -- Dr. Jason McDonald (macadder on FreeNode) _______________________________________________ Development mailing list [email protected] https://lists.qt-project.org/listinfo/development
