It's been 5 days since the 6.1.2 patch and there are still player who CANNOT access their toons to play the game because of this issue (Quick Play Mode and incomplete download/installation). There are now multiple forum threads about it, but this is the original one that should be tracked. There appears to be no response from Bioware since they said that they're aware of the issue. As paying players expected this bug to be prioritized as Critical and that we'd see a patch to resolve in within 24 hours of the 6.1.2 release.
In our guild on the Star Forge server about 10-20% of our active members that I know about, are experiencing this issue -- they can't play the game as of today because of this issue. I'm assuming we're not an unusual guild, so I'm assuming that a large number of players are in the same situation, if they're like our guildies, they're getting angry and frustrated. The software tells them that they can play toons on starter planets. That might have been an acceptable for a day, not nearly a week. That's not really being able to play the game -- it's not even a poorly applied band aide. They've submitted support tickets which have not been responded to. You might think that only 10-20% of the player base being affected isn't so bad, BUT you'd be wrong, because it's not just the players experiencing the bug that are affected. Since they can't play, their friends and guild mates, their raid teams, and their pvp teams are ALL AFFECTED by this bug. And we're all getting frustrated and angry at the lack of response to this issue.
5 days of paying for subscription without being able to use it and with no communication as to when it will be resolved or how they will be compensated is not an acceptable way to treat customers. When will the fix be available? Please tell us that you're not going to turn on the new Swoop content before you resolve this issue for players! Bioware should be thinking about how it's going to make it up to the affected players. They should also look into how they're going to prevent this issue from recurring again, as this seems to happen every few patches. Automated testing and regression testing should catch this before it ever makes it into production.
If you can't reproduce the issue in your dev/test environments and you need more detailed info, then screen share with some of the players experiencing the issue. I'm sure you'd get volunteers if they thought it would help them get back into game sooner.