Tyler T Atlassian Team

The CURL your pasted is the issues import API which is used to upload a zip file of issues. https://developer.atlassian.com/bitbucket/api/2/reference/resource/repositories/%7Bworkspace%7D/%7Brepo_slug%7D/issues/import Try this API instead:…

To create a new issue, you will need to use this API: https://developer.atlassian.com/bitbucket/api/2/reference/resource/repositories/%7Bworkspace%7D/%7Brepo_slug%7D/issues#post

It is fixed now. Thank you again for your patience.

It is fixed now. Thank you for your patience.

@ILI.DIGITAL AG You are correct. Sorry this issue is still affecting you. If you do not have a workspace with the same slug as your username, there will still be an error. This remaining issue was discovered earlier today and a fix is being rolled out right now. I will update this thread once it is completely fixed. Thank…

Hi @agiannone , sorry you are having an issue! We have identified the bug and are working to roll out a fix as soon as possible. I will update this post when it has been resolved.

The bug has been fixed, thank you for your patience. ✅ Please reply to this thread if you experience any further issues.

The bug has been fixed, thank you for your patience. ✅ Please reply to this thread if you experience any further issues.

Sorry about your issue! A fix is in progress. Please follow this other Community post for updates: https://community.atlassian.com/t5/Bitbucket-questions/Why-can-t-I-accept-transfer-of-a-repository-from-another-account/qaq-p/1369855

Sorry about your issue! A fix is in progress. Please follow this other Community post for updates: https://community.atlassian.com/t5/Bitbucket-questions/Why-can-t-I-accept-transfer-of-a-repository-from-another-account/qaq-p/1369855

Sorry everyone, unfortunately a bug was introduced recently and we are working now to roll out a fix. Please follow this post for updates.

https://www.atlassian.com/company/careers

@Bogdan_Onyshenko please check again, the size should be reduced.

Hi @Rakesh Dube welcome to the Community. Here is some documentation on how to reduce your repository size: https://confluence.atlassian.com/bitbucket/reduce-repository-size-321848262.html After completing the steps, it may take some time for garbage collection to run on the repository. After that happens, you should see a…

Hi @Laura A. , sorry about that! It looks like there is a bug, but in the meantime you can workaround it by adjusting the snippet clone URL. Update it as follows: git clone git@bitbucket.org:snippets/<workspace-id>/<snippet-id>/<snippet-name>.git Thank you for post. Our team will work on fixing that ASAP. 

Hi @timothy.harris , welcome to the Community! Here is the Bitbucket Cloud documentation: https://confluence.atlassian.com/bitbucket/branch-permissions-385912271.html If you create a branch permission and leave Allow rewriting branch history unchecked, this will prevent force pushes to that branch.

Hi @Ellen_Sebastian and welcome the Community! From my end it looks like the repository size has gone down. It may have taken some time for garbage collection to run after you updated the repository. Are you still having an issue?

Hello @Shantharam , welcome to the Community! Git doesn't really have a concept of sub-branches. You could look at git tags as a way to further organize your work: https://www.atlassian.com/git/tutorials/inspecting-a-repository/git-tag Right now, all of your branches will show up in that dropdown if they have been pushed…

Hello @Nikita Tratorov , are you still experiencing this issue? Sometimes it can take time for the size the update after pushing to your repository.

If it is loading faster in incognito mode it might help to reset your cookies and local storage. Sorry you are having an issue.

Are you still seeing the issue? Could it be related to the recent Gitlab outage? https://status.gitlab.com/pages/history/5b36dc6502d06804c08349f7 If the error is still happening, it might be best to contact Gitlab support based on the instructions in the error message.

Hi @regan_chan , can you provide a screenshot of the view that is not returning results?

Thank you for all the feedback about the repository transfer instructions causing confusion. We are going to revisit the copy and make an improvement!

It might be most helpful to have our support team look at your specific instance to identify why it is not happening automatically. You can open a support ticket here: https://support.atlassian.com/contact/#/

No, the API only accepts content.raw when POSTing. However, if you are using the web interface to add comments and then GET them using the API, you can retrieve an HTML version of the comment.

Yes, using the Prevent -> Rewriting history setting probably something you want to keep set on master. Your original issue was the the pull request didn't update in your feature branch. If you are still having an issue I recommend you open a bug report with the support team so they can investigate this…

If you are working with Bitbucket Server, the instance should take care of garbage collection automatically. You can trigger garbage collection manually using the directions found here: https://confluence.atlassian.com/bitbucketserverkb/how-to-perform-a-manual-garbage-collection-on-a-repository-867194296.html If you…

As Mikael has said, creating and editing pull requests in Bitbucket Cloud use the same form. This allows you to edit the destination branch. https://confluence.atlassian.com/bitbucket/create-a-pull-request-945541466.html

Are any of those options set? The rewriting history setting could be affecting your force-push issue.

It sounds like you may have tried to visit the website using http rather than https. Be sure to use https when accessing the Bitbucket website: https://bitbucket.org/