Page MenuHomePhabricator

Duping a bug requires a comment
Closed, ResolvedPublic

Description

Can't mark bugs as duplicates easily anymore.

It says "You have to specify a comment when changing the status of a bug from NEW to RESOLVED.", however automatic comment "This bug has been marked as a duplicate of bug XXX" is more than adequate in this case.


Version: unspecified
Severity: normal

Details

Reference
bz27464

Event Timeline

bzimport raised the priority of this task from to Low.Nov 21 2014, 11:20 PM
bzimport set Reference to bz27464.

No idea where this change came in. Chad did look and said the settings look right...

Bz doesn't allow you to say whether something requires a comment or not depending on the *type* of resolution. It only allows you to say, "when this is resolved, it requires a comment."

I don't see that anywhere and Google isn't much help in locating it. (I'm avoiding downloading a Bz tarball.) Can this be changed in the webUI?

This seems to happen for all status changes to RESOLVED, regardless of whether the resolution is DUPLICATE or something else. Of course the duplicate case is particularly stupid, but the workflow of 1) add "Fixed in r12345" comment 2) submit 3) realize you've forgotten to set RESOLVED FIXED 4) be forced to put in another comment is also not very nice.

(In reply to comment #7)

This seems to happen for all status changes to RESOLVED, regardless of whether
the resolution is DUPLICATE or something else.

Yes, this wasn't how it was before. And I'm wondering if this happened as a result of an upgrade or if someone played with the settings.