periodic auto actions on bug tracker

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

periodic auto actions on bug tracker

Ben Coman
I support the auto-closing of old tickets to avoid bug bankruptcy.  Sometimes things seem more important at the time and when my own tickets come back around I get to be more analytical about the effort/reward balance.

It would be useful to expand this a bit to have a quarterly mail out saying something like "Is this issue still important to you?  Try socializing it on the pharo-dev mail list.  Issues going twelve months without interaction will be auto-closed".  Then its not a bad surprise to new users when their ticket is auto-closed.

cheers -ben


Reply | Threaded
Open this post in threaded view
|

Re: periodic auto actions on bug tracker

Tim Mackinnon
It’s a great idea - I too have a good look at what I previously reported and decide if it’s still relevant and whether it makes sense to still pursue it.

Sent from my iPhone

> On 9 Dec 2018, at 06:20, Ben Coman <[hidden email]> wrote:
>
> I support the auto-closing of old tickets to avoid bug bankruptcy.  Sometimes things seem more important at the time and when my own tickets come back around I get to be more analytical about the effort/reward balance.
>
> It would be useful to expand this a bit to have a quarterly mail out saying something like "Is this issue still important to you?  Try socializing it on the pharo-dev mail list.  Issues going twelve months without interaction will be auto-closed".  Then its not a bad surprise to new users when their ticket is auto-closed.
>
> cheers -ben
>
>


Reply | Threaded
Open this post in threaded view
|

Re: periodic auto actions on bug tracker

Marcus Denker-4
In reply to this post by Ben Coman


> On 9 Dec 2018, at 01:50, Ben Coman <[hidden email]> wrote:
>
> I support the auto-closing of old tickets to avoid bug bankruptcy.  Sometimes things seem more important at the time and when my own tickets come back around I get to be more analytical about the effort/reward balance.
>
> It would be useful to expand this a bit to have a quarterly mail out saying something like "Is this issue still important to you?  Try socializing it on the pharo-dev mail list.  Issues going twelve months without interaction will be auto-closed".  Then its not a bad surprise to new users when their ticket is auto-closed.
>

Yes, that is a good idea.

I will add it to the things to do for the issue tracker / integration related scripts.

        Marcus
Reply | Threaded
Open this post in threaded view
|

Re: periodic auto actions on bug tracker

Sean P. DeNigris
Administrator
Marcus Denker-4 wrote
>> I support the auto-closing of old tickets to avoid bug bankruptcy
> ...
> Yes, that is a good idea.

I thought we already did that. Don't we even have a stale/timeout tag to
distinguish from other reasons for closing and help find them again later if
needed?



-----
Cheers,
Sean
--
Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Cheers,
Sean
Reply | Threaded
Open this post in threaded view
|

Re: periodic auto actions on bug tracker

Marcus Denker-4


> On 13 Dec 2018, at 03:35, Sean P. DeNigris <[hidden email]> wrote:
>
> Marcus Denker-4 wrote
>>> I support the auto-closing of old tickets to avoid bug bankruptcy
>> ...
>> Yes, that is a good idea.
>
> I thought we already did that. Don't we even have a stale/timeout tag to
> distinguish from other reasons for closing and help find them again later if
> needed?
>

We close them with a timeout tag.

But we do not send a public mail “hey, these tickets will be closed next week”.

Only the *owner* gets a message on closing.

        Marcus