This was only slightly touched in T259#11 and discussed in today's meeting, hence creating a dedicated ticket.
Tentatively setting Mukunda as assignee (IIRC).

Likely also applies to RT; covering Bugzilla here:
After importing tickets from Bugzilla where an account is identified by an email address and could be reporter/author, CC, assignee, commenter (and voter but ignoring that as we cannot easily convert votes to tokens, see T88 and T432) people need to be able to claim their imported accounts in Phabricator.

A job to update such metadata does not exist yet.

• <epriestley> chasemp: if you subclass PhabricatorWorker and implement your notify/import logic there, you can queue a task with PhabricatorWorker::scheduleTask(...) and it will process in the daemon queue. And you'll get retries / error recovery, queuing, and visibility. When you schedule the task, you can pass parameters (e.g., user X just verified email Y) and then read them when the job executes (the "task data"). And your subclass can be in your library, so you'd only need a 3-5 line patch to actually schedule the worker.
• using API vs internally (but Phab does not allow changing a task's author via its API)
• cronjob? performance? (Bugzilla has ~71000 tickets, ~19700 user accounts, and ~550 active users per month)
• After having something in place, document how users can claim their contributions on https://www.mediawiki.org/wiki/Phabricator/Help