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
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, taskphabricator.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@
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
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.

Status:

Known issues
If an RT ticket had several requestors, only the first person was set as Author in the corresponding Phabricator task. Further requestors were not imported. This means that further requestors do not receive notifications. This regression affects 60 open/new/stalled tickets. See T84828.