Bug 1364

I can't find how to change that.

There is a page to define which status transitions require a comment :
https://bugs.mageia.org/editworkflow.cgi?action=edit_comment
But it's only possible to select "RESOLVED" as status, not "RESOLVED DUPLICATE".

CC: (none) => boklm

Hmm, there is an option commentonduplicate on this page :
https://bugs.mageia.org/editparams.cgi?section=bugchange#duplicate_or_move_bug_status

but it's already set to "off".

(In reply to comment #1)
> There is a page to define which status transitions require a comment

Do the transitions to RESOLVED require a comment?

test

Status: NEW => RESOLVED
Resolution: (none) => FIXED

test2

Status: RESOLVED => REOPENED
Resolution: FIXED => (none)

The way it is now in Mageia bugzilla:
- Reopening a report requires a comment
- Closing as Resolved Fixed/Duplicate requires a comment

(In reply to comment #6)
> - Closing as Resolved Fixed/Duplicate requires a comment

So it works as expected as you just said it's configured to require a comment when closing as RESOLVED.

Yes, but somehow the mandriva bugzilla (at least the version before their last update/revamp), it was possible to close as a duplicate without commenting.... IIRC at least.

See upstream bugs.

Status: REOPENED => NEW
See Also: (none) => https://bugzilla.mozilla.org/show_bug.cgi?id=463453, https://bugzilla.mozilla.org/show_bug.cgi?id=474974

So we have to wait till https://bugzilla.mozilla.org/show_bug.cgi?id=474974 gets resolved somehow, filed on 2009-01-23, more than two years ago...

Maybe commentonresolve=true should be removed from the Mageia bugzilla setup, it's too bloody annoying having to add something when bugzilla automatically says all there's to say:
"This bug report has been marked as a duplicate of ###"

But that would be a step backwards, meaning anyone can close a report without justifying the action.

Or better, patch out bugzilla to restore the old/more-logical behaviour (my coding fu is null, though).

It shouldn't be very hard to customize this for Mageia Bugzilla.

> It shouldn't be very hard to customize this for Mageia Bugzilla.

Be my guest :D

Nothing changed upstream

CC: (none) => marja11

I don't think this is a big problem. It's always good to write a few words for the bug reporter, who didn't notice there already was a bug report for his/her problem, but all the same took the time to report it. "Thanks to have reported this bug. There's already an open bug report for it, I invite you to add yourself in the CC list and comment on it if you have useful information to add to it."

CC: (none) => stormi

When a bug is marked as duplicated of another one, the bug reporter is not automatically added in the CC list of the other bug report ?
This is what happens in other bug track systems (like in kde)

CC: (none) => dglent

(In reply to comment #14)
> When a bug is marked as duplicated of another one, the bug reporter is not
> automatically added in the CC list of the other bug report ?

Yes, that's automatic.

(In reply to comment #13)
> I don't think this is a big problem. It's always good to write a few words for
> the bug reporter, who didn't notice there already was a bug report for his/her
> problem, but all the same took the time to report it. 

I don't see the problem, either. I'll add this bug to the Bug Squad tracker. If any current triagers feel the same as Ahmad, they can speak up and else this bug can be closed.

Blocks: (none) => 3046

All of the current triagers who commented here or on the ml, think it is good to add a comment.

Leuhmanu is improving a script to add a good comment,that'll say something like: "This particular issue has already been reported in our bug tracking system, but please feel free to report any further bugs you find. In general it is welcome to search for existing reports first to avoid filing duplicates."

Closing this bug report

Status: NEW => RESOLVED
Resolution: (none) => WONTFIX

fixed in fact..

Resolution: WONTFIX => FIXED