https://bugs.documentfoundation.org/show_bug.cgi?id=150372
--- Comment #36 from Buovjaga <[email protected]> --- (In reply to Philippe Cloutier from comment #35) > (In reply to Buovjaga from comment #34) > > (In reply to Philippe Cloutier from comment #33) > > > (In reply to Buovjaga from comment #32) > > > > (In reply to Philippe Cloutier from comment #31) > > > > > (In reply to Buovjaga from comment #30) > > > > > > In any case, this report does not vanish > > > > > > when closed, duplicates can and should be re-tested after a fix, if > > > > > > there is > > > > > > suspicion of remaining issues. > > > > > > > > > > It is unclear what you mean by "this report does not vanish when > > > > > closed", > > > > > but duplicates cannot be "re-tested", no. > > > > > > > > What is unclear about it? > > > > > > It is unclear what you mean by "closing a report". > > > > Changing the status to resolved or closed. > > It's unclear how a report could be closed, but there is no such status. If you click the "Status" link next to the status selection drop down, you are taken to a help page: https://bugs.documentfoundation.org/page.cgi?id=fields.html#bug_status Under the section "Closed Bugs" you will find an explanation. In addition to the default RESOLVED and VERIFIED closed statuses, TDF Bugzilla has an additional, literal CLOSED status, which can be accessed after a report has been closed as RESOLVED. In practice at the moment, the difference is it has anti-spam properties: when a report is CLOSED, anyone posting a link to it will get banned. So we use it for reports that attract automated spam (even though the status existed in the tracker before this use). -- You are receiving this mail because: You are the assignee for the bug.
