Phabricator/versus RT
RT is/was a tool based on Request Tracker used by the Wikimedia Operations team for managing day to day tasks. Since December 18, 2014 these processes are handled via Wikimedia Phabricator, with two exceptions: the access-requests@ and procurement@ queues, which are still handled in RT and will be moved to Phabricator at a later stage.
Submitting requests to the Operations team
[edit]Requests to the Operations team are submitted through the regular process of creating a task in Phabricator and associating it to the #Operations project.
If you really miss sending requests to Ops via email, task
phabricator.wikimedia.org including "#Operations" will work as well, but submissions through the website are preferred. Do not use the now deprecated @rt.wikimedia.org email addresses.
access-requests@ and procurement@
[edit]Remember, the exceptions to this norm are access-requests@ and procurement@, the two RT queues that will be migrated at a later stage.
RT data migrated to Phabricator
[edit]This section lists the fields available in RT tickets and their corresponding field in Phabricator tasks.
Note that historical changes in RT tickets (i.e. people that got removed from CC at some point) were not imported. The tickets imported from RT into Phabricator reflect the situation at the time of the migration.
| RT Field | Migrated | Added to description | Not migrated | Notes |
|---|---|---|---|---|
| ID |  |
There were already 78841 tasks in Phabricator so numbers were already assigned (cf. T857). If you know the ID of an RT ticket (e.g. RT #12345), use the "Reference" field in Maniphest's advanced search by entering "rt" followed by the ID (e.g. "rt12345") to find the corresponding task in Phabricator. | ||
| Summary | |
|||
| Status | |
See the Status table below this one for details. Although an RT ticket could get "merged" into another ticket, this was not expressed via a status [sic!]. | ||
| Priority | |
Not imported (not much used in RT); set to "Normal" in Phabricator for imported RT tasks (could be revisited if needed; populating priority on these wouldn't be terrible) | ||
| Queue | |
Converted to projects with "ops-" prefix. | ||
| Dates | |
Dates of comments and the creation date of a ticket are kept. | ||
| (Time) Worked, Starts, Started, Last Contact, Due | |
Not imported — no equivalent and nothing really to do with it | ||
| Tags ("hackathon", "hardware failure"), Third party ticket, Wikitech | |
Not migrated as fields but still visible as comments (e.g. "tags hardware failure added by johndoe"). | ||
| Bugzilla ticket | |
Added to task description with links | ||
| Owner | |
Converted to "Assigned to" | ||
| Requestor(s) | |
Converted to "Author" (and also added to Subscribers due to technical constraints). Known issue: If a ticket had several requestors, only the first one was added as Author. Further requestors were not imported. This regression affects 60 open/new/stalled tickets. See T84828. | ||
| "Cc" and "Admin Cc" | |
converted to "Subscribers" | ||
| Referred To By/Refers To | |
|||
| "Children"/"parents" and "depends on"/"depended on by" | |
Converted to "Parent tasks"/"Subtasks" (in the edit menu), listed as "Task Graph" (in the user interface) | ||
| Attachments | |
Attachments were migrated. | ||
| Comments | |
Comments have been imported, including inline history ("Status changed", "send update email to receipients stuff", etc.) comments. |
Status:
| RT | Phabricator |
|---|---|
| New | Open |
| Open | Open |
| Stalled | Stalled |
| Resolved | Resolved |
| Deleted | Invalid |
| Rejected | Declined |
Known issues
[edit]None
See also
[edit]- RT-Migration project in Phabricator
- wikitech:RT