Roundup Tracker - Issues

Message5905

Author ber
Recipients ber, justus.winter, rouilj
Date 2016-09-30.13:56:57
Message-id <1475243818.91.0.294697929881.issue2550926@psf.upfronthosting.co.za>
In-reply-to
Hi Justus, hi John,

the code for these state changes is part of the configuration,
thus it is part of the standard template bugs.gnupg.org is using.
roundup/share/roundup/templates/classic/detectors/statusauditor.py

You could change the logic in there for your tracker.
Some trackers switch it off alltogether. 

I think "chatting" often means that some activity has started on the
issue and action is needed. This is why "resolved" and "done-cc" switch
to it. When searching for new or chatting issues you should find all
that require user input.

For the use in bugs.gnupg.org where most users can only modify the
issues they have created themselfs, I agree that it may make sense to
not switch
to chatting if the status is new and the new message comes from the creator
of the issue. If you peek at statusauditor.py you probably figure out how
to add that logic.

So I'm unsure if we should change the default for roundups distributions.
Regards,
Bernhard
History
Date User Action Args
2016-09-30 13:56:58bersetmessageid: <1475243818.91.0.294697929881.issue2550926@psf.upfronthosting.co.za>
2016-09-30 13:56:58bersetrecipients: + ber, rouilj, justus.winter
2016-09-30 13:56:58berlinkissue2550926 messages
2016-09-30 13:56:57bercreate