Identify types of links to Bugzilla which should be redirected or updated to Phabricator
Closed, DuplicatePublic
Actions

Assigned To

None

Authored By

	• flimport
	Jun 15 2014, 9:44 AM

Description

Currently 2332 links on mediawiki.org alone.
https://www.mediawiki.org/w/index.php?title=Special:LinkSearch&limit=5000&offset=0&target=https%3A%2F%2Fbugzilla.wikimedia.org%2Fbuglist.cgi
https://www.mediawiki.org/w/index.php?title=Special:LinkSearch&limit=5000&offset=0&target=http%3A%2F%2Fbugzilla.wikimedia.org%2Fbuglist.cgi

For more: https://wiki.toolserver.org/view/MySQL_queries#List_of_external_links_from_all_wikis

We need a map of all subtypes of links; probably the best way is to make strict apache rewrite rules which match only what they're sure to be able to translate meaningfully to phabricator URLs, then run them on the full list of known URLs and see what's not yet matched. When something is not immediate to match, a sub-task needs to be filed to make it possible.

Example challenge: http://fab.wmflabs.org/T171#15

Reference: http://www.w3.org/Provider/Style/URI.html

Details

Reference: fl417

	Title	Reference	Author	Source Branch	Dest Branch
	Rename jenkins-slave to jenkins-agent	repos/releng/jenkins-deploy!29	hashar	jenkins-agent-user-rename	master
	data.yaml: introduce mariadb image for jobs-framework	repos/cloud/toolforge/image-config!4	aborrero	mariadb	main

Customize query in GitLab

Related Objects
Search...

Status	Assigned	Task
Duplicate	None	T254 Identify types of links to Bugzilla which should be redirected or updated to Phabricator
Declined	Aklapper	T105 Can't find a way to customise search results display
Resolved	None	T176 Adapt on-wiki bug templates to point to Phabricator
Resolved	Qgil	T177 Update the {{tracked}} template to accept Phabricator parameters
Resolved	Qgil	T454 Add phabricator to the interwiki map
Resolved	Qgil	T168 Port {{mw:Extension}}'s bugzilla section links to Phabricator
Resolved	• Mattflaschen-WMF	T539 Adapting Gadget-BugStatusUpdate.js to Phabricator
Resolved	Aklapper	T88953 Please create bot for phabricator-bug-status
Declined	Aklapper	T240 Map from bugzilla aliases to phabricator tasks

Event Timeline

aklapper wrote on 2014-06-23 19:49:43 (UTC)

I don't see redirecting all links as a good use of time and I don't see T171 blocking this.
We will redirect show_bug.cgi for ID parameters (for completeness, further parameters such as "ctype=xml" are available but neglectable).
Redirecting show_bug.cgi with an Alias parameter (T402) looks also doable (but I cannot judge the performance of another 90 Apache Redirect rules).

Redirecting buglist.cgi is way more complicated as URL parameters could be really anything in Bugzilla (resolutions, products, components, keywords, very interesting complex search parameters for some Bugzilla elements that we will kill, like the useless "Mobile Platform" custom field in Bugzilla, see https://bugzilla.wikimedia.org/show_bug.cgi?id=41197#c5 ) and I currently don't see a feasible plan for this (though I'd love to be proven wrong).

I wonder if we can somehow extract and identify any kind of commonly and recently used URL patterns for buglist.cgi that could be worth to support, like bug_id=1,2,3 parameters, or something like "{all open statuses in Bugzilla} && {Bugzilla component X, Bugzilla component Y, Bugzilla component Z}" if that is a common usecase, if we end up with some static mapping between these elements in Bugzilla and in Phabricator. Depends on how we end up solving T68 and T423.

Again: Zero breakage of links is unrealistic.
The question is how to identify common queries, and then the tradeoff question is how to minimize breakage for common queries vs. not spending ages on coming up with redirects for everything and the kitchen sink.

aklapper wrote on 2014-08-12 18:08:56 (UTC)

We need a map of all subtypes of links;

Nemo: Could you elaborate what this exactly means? Do you want a list of all top-level .cgi's in Bugzilla, or what is asked for?

To summarize (might be incomplete) how I currently see things:

We plan to handle T65: Redirect URLs which point to a single ticket in Bugzilla.
https://bugzilla.wikimedia.org/index.cgi should go to https://phabricator.wikimedia.org/
https://bugzilla.wikimedia.org/query.cgi should go to https://phabricator.wikimedia.org/maniphest/query/
https://bugzilla.wikimedia.org/reports.cgi and https://bugzilla.wikimedia.org/report.cgi and https://bugzilla.wikimedia.org/chart.cgi should all go to http://phabricator.wikimedia.org/fact/
https://bugzilla.wikimedia.org/describecomponents.cgi should go to http://phabricator.wikimedia.org/project/query/all/
https://bugzilla.wikimedia.org/buglist.cgi can have dozens of URL parameters, and can have hundreds of parameters. Using buglist.cgi with a bug_id parameter plus a number of bug IDs with commata inbetween (to get a static list of tickets listed) probably isn't too common. Queries for a specific status (open tickets) in some specific products/components are probably more likely, but I don't consider it doable to have a mapping between Bugzilla products and components and Phab projects somewhere publicly stored, which could be accessed to "on-the-fly" turn that unlimited number of potential URL parameters into some query that more (or rather less) would even show similar results in Phabricator. The way search results (and their URLs) are created are just too different. Proposing WONTFIX for this part (though I'd be really happy to be proven wrong).