An issue related to this was reported here.

Another issue relate to this was reported here.

One more issue related to this was reported here: a user unable to pick a topic to translate during a campaign.

Issues related to this were reported here.

This comment illustrates a user having trouble to find an article not already being translated by someone else.

This issue was also mentioned in T144444: ContentTranslation bug - collective translation

Hi, two news reports : on my talk page about one of mine translation draft, and on MW site Talk:Content translation.

This issue was reported in this comment.

Another report of this issue.

One more report of this issue.

And one more. I seem to remember a brief period when creating your own translation was possible? Was that an experiment or do I just remember wrong? Currently there is no way to do this as far as I can see

Another issue in which the user is same but forgot the password of old account.

Why is the tool breaking one of our most important, long standing and cherished policies, namely https://en.wikipedia.org/wiki/Wikipedia:Ownership_of_content, and allowing the first mover to take over some level of ownership and control of an article in translation.

Also, the tool is abysmal, it does nothing but churn out error after error. I've no idea why it's enabled in Beta Features, because it looks like it's barely into Alpha let alone out and into Beta.

In T86151#4842047, @Nick wrote:

Why is the tool breaking one of our most important, long standing and cherished policies, namely https://en.wikipedia.org/wiki/Wikipedia:Ownership_of_content, and allowing the first mover to take over some level of ownership and control of an article in translation.

This is a limitation of the current data model that we plan to resolve. This ticket captures a proposal for doing so.

Also, the tool is abysmal, it does nothing but churn out error after error. I've no idea why it's enabled in Beta Features, because it looks like it's barely into Alpha let alone out and into Beta.

Content is very different from wiki to wiki. The tool has been very useful for many users on different wikis while others have experienced different issues on some articles on different wikis. We are working on a new version of the tool that is intended to provide a more solid editing experience. Since we cannot test all combinations of article × source language × destination language individually, it is very useful to hear about specific examples of the issues. Feel free to report any issue with the new version (the old one will be deprecated soon) in the project talk page or here in Phabricator.

In T86151#4842911, @Pginer-WMF wrote:

the old one will be deprecated soon

We've been hearing that for at least 2 years, during which the tech ambassadors had to do the tech support that the team refused to do.

Do you at least plan to test bugs filed against v1 on v2, so we don't have to report the same issues again?

In T86151#4843285, @Strainu wrote:

In T86151#4842911, @Pginer-WMF wrote:

the old one will be deprecated soon

We've been hearing that for at least 2 years, during which the tech ambassadors had to do the tech support that the team refused to do.

As mentioned in T204817#4842893, the new version is being used for 45% of the translations. As new improvements are made we have been exposing the new version more prominently, and we plan to make it the default during next January. The new version replaces the editing surface used in version 1 (the browser default editing surface) with the Visual Editor one (more apt to deal with wikitext), which required to significatively refactor the different tools that manipulated the editing surface. So it has been a significant change and we wanted to expose the new version gradually.

Do you at least plan to test bugs filed against v1 on v2, so we don't have to report the same issues again?

Yes. We are already doing so. We have a process to review reported issues where we either (a) check that they are resolved with the new version, or (b) confirm that the issue still affects the new version. Recently we have been reviewing tickets related to references and templates which were the focus of the recent improvements in the new version, but we'll be covering other areas.

I just noticed one user complained they can't create an article which is already started in CX by another user (while that user retired, so it's highly unlikely they'll complete that article). Currently, we're forcing them to wait 455 days for the draft to be automatically purged, which is crazy. Can this be prioritized?