Last modified: 2013-01-01 00:51:26 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 T40671, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 38671 - "fixme" button to automatically file bug
"fixme" button to automatically file bug
Status: NEW
Product: Wikimedia
Classification: Unclassified
Git/Gerrit (Other open bugs)
unspecified
All All
: Normal enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks: 38239
  Show dependency treegraph
 
Reported: 2012-07-25 13:44 UTC by Nemo
Modified: 2013-01-01 00:51 UTC (History)
2 users (show)

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


Attachments

Description Nemo 2012-07-25 13:44:23 UTC
Bug 35534 is not going to be fixed in any foreseeable future and it's very urgent to replace the "fixme". Gerrit has no way to keep track of whether a code review comment or -1/-2 has been really addressed, and after the fact reviews are just message bottles thrown into the ocean (while -2 is not possible).

Our only option seems to be bugzilla. Therefore we need an easy way to file bugs, like a button which automatically opens a bug form with a standard summary, a link to the change, the committer as assignee etc., and leaves a dummy review with a link to the bug.
If it's a problem to map projects->components, then we could use a dummy one.

Use case: we have dozens or hundreds of commits which need follow-up to fix badly worded system messages or to add documentation, even a "fix messages" button would be worth it.
Comment 1 Sam Reed (reedy) 2012-07-25 14:03:46 UTC
This will have to wait until the next major Gerrit release, which has the ability to support plugins, so we don't have to get into the mess that core hacking brings
Comment 2 Chad H. 2012-07-25 14:07:56 UTC
(In reply to comment #0)
> Bug 35534 is not going to be fixed in any foreseeable future
>

This is not true. Just earlier this week I pushed some changes upstream to begin the work needed to support freeform tagging (both to get the work started and get the discussion going). However, that's not a reason to also possibly add a tool here.

(In reply to comment #1)
> This will have to wait until the next major Gerrit release, which has the
> ability to support plugins, so we don't have to get into the mess that core
> hacking brings

Also not true--someone with JavaScript chops could whip up something here and we could deliver it in the site-specific HTML within Gerrit. Furthermore, 2.5 plugins don't expose GWTUI yet, so doing UI goodies like this wouldn't be done as a plugin.

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


Navigation
Links