I'm not sure if I fully understand how these are supposed to work, but my intuitions can't be too far off. Here are my experiences:
I first created a patch queue for my test fork of cx (http://bitbucket.org/ches/cx-ches/), called cx-ches-patches. I forgot to check the option to omit the series file, so I deleted the repo and tried to create a new patch queue with the same name, only choosing the omit option this time. The creation stalled, and still shows the barber pole when I try to visit the page for the repo.
I created another patch queue called cx-ches-patches2. Honestly, I think I might have forgotten to omit the series file again (it shows an 'Automated Init' changeset -- is that what that should be? Doesn't seem to actually have a series file though -- see
#61 maybe). I pushed an existing mq patch repository to this successfully, and can clone the repo now. However, on bitbucket it appears to be empty.
Finally, I created a private patch queue for a private repository. This time I definitely omitted the series file and the repository shows zero revisions on bitbucket. Again, I successfully pushed an existing mq patch repo here and can clone it, but it still shows up as empty on the web.
Have I done something wrong? Hope this report is useful in troubleshooting.
Bitbucket is great so far, keep up the good work!