Similarly, I noticed

flimport added a comment.Via Conduit · Sep 11 2014, 10:40 PM
Comment Actions
Rush wrote on 2014-07-11 14:07:57 (UTC)
(...)

on T264.

These actions are supposed to be assigned to the actual author as soon as the user registers with the Bugzilla email address and bzimport completes the claiming activity job.

You can see that chasemp and Qgil have their comments correctly assigned at https://bugzillapreview.wmflabs.org/T1 , while right now aklapper's actions still are attributed to bzimport. This will change when the bot goes through Andre's actions.

Leaving open this task just to make sure that this effectively happens in bugzillapreview, but it shouldn't be a problem. Just give a bit of time to bzimport.

Just as expected, this works. Now JamesF has his Bugzilla history properly linked to his Phabricator account. You can see how his comments at https://bugzillapreview.wmflabs.org/T4262 are now assigned to him.

The workflow we currently have is the best technical compromise we have been able to find. Creating accounts on behalf of users by launch date has its problems too, which we consider bigger.

The principles and compromises of the current workflow have been discussed at length at T572: Determine the fate of comment metadata from legacy systems in phabricator.wikimedia.org. You can start reading at T572#10081

We haven't discussed what to do with the users and the actions that haven't been claimed after a while. I don't have an informed opinion, but maybe a possibility is create accounts on behalf of the inactive users down the road, say six months after the Bugzilla migration?

I must be able to search reports according to their reporter whatever the fate of the reporter was

Imagine that you need to search all the tasks authored by DanClemmensen, a user that (as of today) hasn't claimed his Bugzilla history. As soon as T75743 is fixed, searching for "Author: DanClemmensen" should provide a list of tasks where such string exists, which is probably the list of tasks you would be looking for.

We cannot time-travel to change the migration logic, proposing "declined" here again.

Or this task could be kept open to figure out how to get everyone with actions to register.

In T847#983701, @Nemo_bis wrote:

figure out how to get everyone with actions to register.

More people helping: https://meta.wikimedia.org/w/index.php?title=User_talk:Herbythyme&diff=prev&oldid=15764752

This is an extremely important defect of our installation and it's very unwise to close the task, especially if the issue is not documented in some visible and frequently checked document and/or assigned to someone actively working on it.

technically not feasible to fix this request.

Sounds extremely unlikely; was upstream consulted on the matter?

https://secure.phabricator.com/book/phabricator/article/configuring_accounts_and_registration/ states that it's possible to register accounts from the CLI.

https://secure.phabricator.com/book/phabricator/article/configuring_accounts_and_registration/ states that it's possible to register accounts from the CLI.

@Nemo_bis: I'm afraid I still don't understand which problem gets solved by creating accounts for people who do not use their accounts (because they would have already registered if they would). The only situation coming to my mind is what you wrote in T847#15087: "I must be able to search reports according to their reporter". Which does not sound like a common use case that would justify efforts.

The CLI functionality described in https://secure.phabricator.com/book/phabricator/article/configuring_accounts_and_registration/ also requires entering an email address for the account to create. AFAIK we do not have these email addresses.

[root@canislupus phab]# ./bin/accountadmin
Enter a username to create a new account or edit an existing account.
    Enter a username: clitest
There is no existing user account 'clitest'.
    Do you want to create a new 'clitest' account? [Y/n] Y
    Enter user real name: CLITEST
    Enter user email address: whatever@foo.bar
    Enter a password for this user [blank to leave unchanged]: 
    Is this user a bot? [y/N] N
    Should this user be an administrator? [y/N] N

ACCOUNT SUMMARY
               OLD VALUE                        NEW VALUE                     
    Username                                    clitest                       
   Real Name                                    CLITEST                       
       Email                                    whatever@foo.bar              
    Password                                    Unchanged                     
         Bot   N                                N                             
       Admin   N                                N                             
    Save these changes? [Y/n] n
Cancelled.

because they would have already registered if they would

This is an incorrect assumption. Users would use Phabricator if they remembered that they have a use for it; not the opposite.

AFAIK we do not have these email addresses.

The email addresses must come from the non-sanitised bugzilla dump, of course. The whole point of this exercise is to recover all the bugzilla email addresses so that I don't have to notify each user manually.

In T847#3061858, @Nemo_bis wrote:

The email addresses must come from the non-sanitised bugzilla dump, of course.

If you refer to T85141, that unsanitized dump does not exist anymore AFAIK? Or do you plan to extract that from the DB behind http://bugs.wmflabs.org ?