_ImportExportCaveats

On this page

Still need help?

The Atlassian Community is here for you.

Ask the community

When using the issue tracker import/export feature to move issues from one Bitbucket repo to another, the issue IDs remain the same. However, the IDs and therefore the permlinks, change. They change because comment IDs, in contrast to issue IDs, are not local to the repo.

During an import, Bitbucket silently uses NULL to replace any foreign keys that it cannot resolve (for example, a username that no longer exists on Bitbucket).

Last modified on Mar 22, 2013

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.