Last modified: 2011-03-08 16:51:39 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T29464, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 27464 - Duping a bug requires a comment
Duping a bug requires a comment
Status: RESOLVED FIXED
Product: Wikimedia
Classification: Unclassified
Bugzilla (Other open bugs)
unspecified
All All
: Low normal (vote)
: ---
Assigned To: Priyanka Dhanda
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2011-02-16 18:15 UTC by Max Semenik
Modified: 2011-03-08 16:51 UTC (History)
4 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Max Semenik 2011-02-16 18:15:13 UTC
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.
Comment 1 Sam Reed (reedy) 2011-02-16 18:32:08 UTC
No idea where this change came in. Chad did look and said the settings look right...
Comment 2 Mark A. Hershberger 2011-02-16 23:59:23 UTC
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."
Comment 3 Chad H. 2011-02-17 00:59:15 UTC
See commentonduplicate.
Comment 4 Mark A. Hershberger 2011-02-17 15:28:01 UTC
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?
Comment 5 Chad H. 2011-02-17 17:38:21 UTC
Yes.

https://bugzilla.wikimedia.org/editparams.cgi?section=bugchange

Next to last item on the page.
Comment 6 Sam Reed (reedy) 2011-02-17 18:00:36 UTC
And it's marked as off...
Comment 7 Roan Kattouw 2011-02-20 20:32:26 UTC
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.
Comment 8 Chad H. 2011-02-20 23:09:09 UTC
(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.
Comment 9 Chad H. 2011-03-08 16:51:39 UTC
I fixed this last week.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links