Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,460,159
Community Members
 
Community Events
176
Community Groups

After using the migration assistant attachments do not work

I just used the cloud migration assistant to migrate from the server platform to the cloud. After the migration I noticed that every attachment on our pull requests was no longer working. The images just say failed to load and when we uploaded txt documents those now just show text where there used to be a link to click and download the file. 

1 answer

0 votes
Patrik S Atlassian Team Jun 14, 2022

Hello @Kevin Holy ,

Welcome to Atlassian Community.

The Bitbucket Cloud Migration Assistant (BCMA) indeed does not currently support the migration of attachments and it currently just copies the filename, not the actual content of the file.

However, we have the following script that might help you with the replication of the attachments in the Pull Requests on your server/DC instance to your Bitbucket Cloud instance :

The process involves locating all attachments within comments by reading any particular PR's activity log. Once we identify the file, we can download it to the local working machine. We replace space characters with underscores, since that will happen anyway when uploading to cloud but we do it early to better keep track of everything, and then we append the PR id (of the PR it belongs to) as well as a random 8 digit hash to the end of the filename (before the file's extension) to make sure it's unique and won't collide with any other files that we previously uploaded. Once the file exists in the new repo's "downloads" folder, we can then hyperlink to it from a new pr comment in the matching prs.

Please note that this tool was NOT written by Atlassian developers and is considered a third-party tool. This means that this is also NOT supported by Atlassian. We highly recommend you have your team review the script before running it to ensure you understand the steps and actions taking place, as Atlassian is not responsible for the resulting configuration.

Hope that helps! Let me know in case you have any questions.

Thank you, @Kevin Holy .

Kind regards,

Patrik S

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
TAGS

Atlassian Community Events