1. Bitbucket
  2. Public Issue Tracker
  3. master
  4. Issues

Issues

Issue #7417 wontfix

issue importer does not transfer watchers on homegrown-zips

Michael Bayer
created an issue

I've migrated my project "alembic" to git, and in so doing I renamed the old project to "alembic_moved_from_hg_to_git", created a new project "alembic", and added the code, as well as the full issue database from the old project using the importer tool.

But all the "watchers" were lost, even though the watchers are in the db-1.0.json file. I had to personally click the "watch" link for all the issues myself, and there is not even an easy way I can send a message to all the previous "watchers" that the issues have all been moved, except for sending a message to all 64 of them individually (a prospect I'm not excited about).

There needs to be some way to get the watchers onto a new tracker once an issue import is performed, either allowing them to go in directly or at least some system of notifying them.

Comments (15)

  1. Michael Bayer reporter

    thanks. I would assume the reason it's like this is to prevent spammers, otherwise someone could fabricate an export file, add in hundreds of watchers, then spam them. So perhaps the importer needs to confirm that each watcher is watching an issue that's part of another project of the same owner.

  2. Erik van Zijst staff

    Michael Bayer You're close.

    When people craft their own zip files, we deliberately ignore any watchers, as it would indeed provide ways to annoy a lot of people very easily.

    However, the zips that we create ourselves are signed (look for the .signature file in the root of the archive) and when you re-import a zip that was created by us, we will restore the watchers.

    If you say that we dropped the watchers even on our own zips, can you send me that zip file? If you don't want to do that publicly here, you can email it to support@bitbucket.org and mention my name and link to this comment.

  3. Michael Bayer reporter

    ah, well the .signature file made it into the new .zip file I created, but the whole point of the migration was to change the changeset ids in the .json, so the signature file certainly doesn't match the .json.

    So yes there's nothing the code is doing that's not by design, but this really sucks that I can't migrate my issue tracker to git along with migrated issues, without losing all my watchers, or even have some way to just tell them all that "we've moved".

    Or if I delete the old tracker and put in a redirect URL to the new one, will they get notified of that ?

  4. Erik van Zijst staff

    So yes there's nothing the code is doing that's not by design, but this really sucks that I can't migrate my issue tracker to git along with migrated issues, without losing all my watchers,

    Well; it's either, or. You can retain all watchers, but yeah then your SHAs will all be wrong.

    Or if I delete the old tracker and put in a redirect URL to the new one, will they get notified of that ?

    Deleting a repo (so you can leave a redirect URL) does not notify anybody. However, when people visit the old deleted repo, they will see the link to the new git repo (note that we do not automatically redirect people, they have to click the link themselves).

  5. Michael Bayer reporter

    OK, I'm sensing that "nothing to do here" vibe, but if folks leave comments on my issues, the other watchers won't be roped in. I guess I can manually send messages if that's the case....thanks for looking into it.

  6. Erik van Zijst staff

    Well, I understand your frustration, but I'm not really sure what we could do about it, short of removing the abuse protection.

    FWIW, if you mention somebody in a comment on an issue, they'll get an email, so as much as it sucks, that could be a little bit of a workaround if you don't have too many participants on an issue.

  7. Emilien Coquard

    Hi Erik van Zijst

    We have just migrated an internal project from GitHub to Bitbucket with 500+ issues.

    That is a real problem that watchers are not kept, we had to remove the assignees manually on each issue and add them again so people are notified.

    We have other internal projects to migrate to Bitbucket, but given the difficulty it was and the time it took to do this operation, we're reviewing our plans.

    I contacted support to ask them if they could manually import the dump with watchers, or generate the .signature file, but unfortunately Jason Worley told me they cannot.

    there is no way for me to deviate from our existing processes.

    Could this issue be reopened?

    For corporate projects in Bitbucket, there is not much concerns about spam. You could allow for example only coworkers as watchers.

    Many thanks for your help!

  8. Log in to comment