@dom_walden
Couple of questions on temp users
(1) in betalabs env, a temp user created on dewiki was able to become an auto-created user (Users group, see[ https://en.wikipedia.beta.wmflabs.org/wiki/Special:Contributions/*Unregistered_4760 on enwiki. I suspect it's just limitations of betalabs. In general though, auto-created temp users would behave as just temp users?
(2) SearchView extension is not installed, but T340626: Update SearchVue for IP Masking requires some checking. There might be other cases of extensions not be present on dewiki betalabs. Any plans to have temp users on other wikis? Cross-wiki functionality should be checked anyway.

In T341839#9014440, @Etonkovidova wrote:

@dom_walden
Couple of questions on temp users
(1) in betalabs env, a temp user created on dewiki was able to become an auto-created user (Users group, see[ https://en.wikipedia.beta.wmflabs.org/wiki/Special:Contributions/*Unregistered_4760 on enwiki. I suspect it's just limitations of betalabs. In general though, auto-created temp users would behave as just temp users?

Because IP Masking is not enabled on enwiki, temporary users created on dewiki will currently behave like registered users on enwiki. We are currently discussing how we want to handle this.

(2) SearchView extension is not installed, but T340626: Update SearchVue for IP Masking requires some checking. There might be other cases of extensions not be present on dewiki betalabs. Any plans to have temp users on other wikis? Cross-wiki functionality should be checked anyway.

Good point. I don't know. @Niharika @Tchanders might know more.

@Etonkovidova - given this is more of a testing Epic than a sprint-level task, how do you want to manage this task? Should we leave it open as an epic under Growth-Team ? Or should we create subtasks to move into the sprint if there is anything specific you are testing.

In T341839#9282066, @KStoller-WMF wrote:

@Etonkovidova - given this is more of a testing Epic than a sprint-level task, how do you want to manage this task? Should we leave it open as an epic under Growth-Team ? Or should we create subtasks to move into the sprint if there is anything specific you are testing.

Yes, let's have it as an open task as a testing epic task under either #Grwoth-Team or, if it's possible, under IP-Masking-Growth-Team. I have the task on my list of tracked priorities, so there is no danger that the task will be lost.