Ulrich Kuhnhardt [IzymesCo] Atlassian Partner

Hi there, it does not make sense why your 3rd party company requires an SEN in order to sell you a Bitbucket cloud subscription or provide a quote. There are instructions [1] on the Atlassian Partner Portal for Atlassian Partners on how to quote and purchase BB Cloud for their clients. If your third party provider is a…

To add reviewers to a pull request in BB DC you can use the update pull request RESt endpoint and simply add the "reviewers": [..] element together with the id and version elements. You need to fetch the current PR status first to obtain the current version. Happy Coding Ulrich // Izymes

Hi Yogesh, you might get a better chance of someone replying by posting your question in https://community.developer.atlassian.com/ Most internal APIs are locked for apps, I'm not sure they can be used from the client (browser) Have you tried this endpoint from your app's backend? The request usually contains a payload…

Hi @John Keippel III I think the core problem you and @Tural Nasirov are alluding to is that any native reviewer configuration, be it 'Default reviewers' or CODEOWNERS adds relevant reviewers at PR creation stage. If the PR is updated (for example a reviewer is removed manually) the same rules don't seem to be applied. Can…

Great app. I wonder if coloured labels extend the native Jira label namespace, i.e. I can use combined labels in label fields including the native Jira label field. Reason: We have a mature and growing Jira label namespace and would like to combine label namespaces after introducing your app.

I concur with @vikram - there are already a lot of git operations like creating branches etc in the pull request REST API and in the repository REST API. In order to perform core git commands like push, pull, checkout etc your app needs to do that locally with a git client. If you need to perform custom git commands on the…

Hello Tural, I understand that you want to enforce a set of reviewers and their approvals as per your codeowners configuration. Merge-checks are enforced with a Bitbucket Premium with $3(base) + $3(premium) per workspace user per month. There are a few alternative apps on the Atlassian Marketplace for BB Cloud, that do…

If you were on Bitbucket server you could add a custom server side pre-receive hook. Since you're on Bitbucket cloud there is no such mechanism in place. There is a 10-year old feature request - https://jira.atlassian.com/browse/BCLOUD-10471 - for allowing server-side pre-receive hook. You are welcome to vote for and watch…

Create a simple Bitbucket server plugin and add the issue collector script as a web-panel in atlassian-plugin.xml like so <atlassian-plugin ... plugins-version="2"> <web-panel location="bitbucket.notification.banner.header" key="kevins.test"> <context>atl.general</context> <resource name="view"…

Hi Rodrigo, If I get this right you are looking for project permissions? Can you add a screenshot that elaborates on the problem? It looks like you can't retro-fit project admin permissions for existing projects. I have tried the following: * Create a bitbucket group with permission "Can create projects in this workspace",…

Expanding on @Syahrul 's response - you can also add merge-checks that enforce reviewer rules. This gives you peace of mind, as PRs can only be merged if the right amount of reviewers have approved. While Bitbucket cloud offers Code Owners which is a file-based reviewer configuration in your repository, you may prefer a…

I come across the same problem quite frequently. I don't know a way to turn this off in the UI. When creating a PR you can use the link that you see when you push the source branch to bitbucket.org (remote) via the git CLI, and add the destination branch as a req param. For example…

I love big trees, this one is in Springbrook NP, QLD

Is this a first install or upgrade or migration to another server? Can you review the complete atlassian-bitbucket.log from server start until the first request? With the complete log you explore solutions by following the links under "Related Community content" on the right hand side.

Hello @Sergio A You may also explore Bitbucket cloud apps on the Atlassian Marketplace that facilitate your pull request review and merge process, including enforcing merge conditions. We have built Workzone for Bitbucket Cloud for enterprise level pull request workflows including * File/path reviewers and groups, added…

Hi Paul, Bitbucket Cloud released Code Owners where you can configure reviewers at branch and file/module level in a .codeowners file that's part of your repository. If you're looking for a more convenient and intuitive UI based approach that lets you configure reviewers for branches, files and modules on a Workspace,…

Hi Mohan, you can only approve/unapprove as the authenticated (logged in) user. Approving/Unapproving on behalf of other users is not possible. There is a similar request and answer here. The next best option would be to (programmatically) copy source & dest branch, description and summary of the existing PR, decline it…

Hi @Mike Quentel The Python script does exactly what I was going to suggest. Locking BBServer * Read branch permission of repo and log it to a file * Set branch permissions in all repos to read_only Unlocking BBServer * Read permissions log file * Apply permissions. Note that as far as my limited understanding of Python…

Hi @Brent Hessell Thanks for sharing your observation. I'm happy to support you with this issue. I think you have set up Workzone correctly. Please be aware that Bitbucket repository default reviewers which are defined outside Workzone are added by Bitbucket. Best way forward is to create a support request with us so we…

Not an answer, just a BIG THANKS to @[deleted] for posting this 'poll' and all the responders! Your contributions are so valuable.

According to the BB Cloud API spec the request returns a 302 to a repository diffstat. 1. Check if you can see the exact PR in the browser, you may not have access to the repo. 2. If you have access in the browser check your app-password scopes are sufficient to see repo and pull requests. 3. Send the request again via…

@Dave Parrish [Atlassian] are you considering adding extension points to PR create page, as @Michael Rüegg _Mibex Software_ suggested?

Hi Harmeet, that's a very good question! I've got a few points that I find important: Defined Ownership: Assign clear ownership of specific modules, components, or services to individual team members or sub-teams via Bitbucket repository or AD groups. This ensures accountability and pride in the team's work. Use the…

Hi @Dave Parrish [Atlassian] looks great. Love the new UI. I must have missed the RFC for this update. In case there wasn't an RFC, we would appreciate if you could add a section for BBCloud RFCs so we can give feedback early - in the 'impossible alone' spirit. 1. I personally find the comment UX a little noisy with…

Hello Ankit, could you please elaborate on the above scenario? For example, why do you need to merge a pull request in a Jira issue? Keen to learn about your use case.

Would love to meet you @Jimmy Seddon ! Expo pro tip: Most vendors have some cool swag to give away, and they don't want to ship it back home after the expo! My favourite last year: Socks from EasyAgile! I think they're back at Team24 this year and I can't wait to stop by their booth. See you all soon!

IMO the key is consistency and repetition in whatever promotion path you choose. We at Izymes try to answer community questions, create a mix of knowledge, info and how-to blog posts in the community and attend relevant ACE events. ACE events may be a great platform to showcase any solutions if it fits the ACE event…

Hi Mohan, this is correct. Workzone specific approval quotas (mandatory or else) are configured in the Workzone 'Merge' configuration for PR target branches or patterns. If you don't specify a merge-configuration (with a quota) for mandatory reviewers, Workzone implies that 100% of mandatory reviewers on the PR must…

Hi Mohan, good news: Workzone adds mandatory reviewer users or groups and enforces only approvals for mandatory reviewers configured in Workzone. Workzone won't interfere with or be interfered by repository default reviewers and min approval count. Bitbucket will run the min approval count merge-check (on repo default…

Hi Mohan, it's Ulrich here from Izymes. if I understand your question correctly you want to make sure that a mandatory set of reviewers is always included in pull requests. So far Bitbucket (DC) lets you define default reviewers and when a PR is created the reviewers list is populated based on default reviewers, HOWEVER…