On Thu, 2 Nov 2006 19:10:13 -0800 Don Armstrong <[EMAIL PROTECTED]> wrote:
> > It seems like a useful message that belongs in the bug log. If > > that's the only problem, then perhaps this bug should be changed to > > to a 'wishlist' bug and retitled "Improvement: add reopen email > > control message to BTS log". > > The effect of the control message is put there, as well as the > original message to control that caused the bug to be reopened. The > parsing of the message isn't included because it's not applicable to > the bug log. If an absence of records regarding some automated function confuses users, (me for one), then is that not a sort of interface bug? While I'm still not sure if I missed an reopen acknowledgement email, it's probable that eventually somebody is going to miss such an email, and that's when a copy on the BTS would be helpful. What's "not applicable" in this context begs the question of what the public BTS is for. Mainly the BTS is for publicly describing bugs. But without the record keeping and event logging the BTS would be less reliable. It's a question of how much logging and recording is enough, too much, or too little. I don't know if there's a general answer, but I know how to scratch where it itches... -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
