access-requests@ hasn't been migrated from RT yet. Let's use this task to follow the progress.
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Declined | greg | T41 Set up redirects from RT URLs to Phabricator | |||
| Declined | • chasemp | T84861 Migrate access-requests@ from RT to Phabricator | |||
| Resolved | • chasemp | T84867 Create "ops-access-requests" project |
Event Timeline
Comment Actions
So migrating the existing content of this queue to Phabricator isn't a priority for us, but given that we'll likely receive most new requests in Phabricator anyway, we'll need to make this work in some shape or form. Let's create this project and figure out a (manual) workflow for now, and optimize it later.
Migrating the existing RT content can happen when we also do the procurement queue; as long as we still can refer to the existing (resolved) tickets in RT itself we should be fine for now.
Comment Actions
Since new requests have been migrated to phab, do we still plan to import the existing old tickets before we shut down RT at some point?
Comment Actions
Wondering who from Ops to make a call what's left / if importing is wanted. Or if noone knows, maybe to bring up in a weekly Ops meeting?
Comment Actions
! In T84861#1365698, @chasemp wrote:
! In T84861#1321088, @Dzahn wrote:
Since new requests have been migrated to phab, do we still plan to import the existing old tickets before we shut down RT at some point?
@mark: Input / decision welcome. (Feel free to reassign after doing so.)
Comment Actions
I'd be inclined to say, not really necessary, as long as we keep a DB backup of RT just in case.
Comment Actions
We have said for now we are not going to do this, RT things will be made available for reference in other ways.