Automate and control your Bitbucket Pull Request Workflow, Reviewers, Approvals and Merge Process
Configure pre-defined reviewers for branches and file patterns. Each Pull Request for that branch will include these reviewers automatically. Optionally define source and target separately to refine the config scope.
Workzone can merge the Pull Request automatically on behalf of a proxy (or real) user when all or a percentage of reviewers have approved. Define target branches or branch patterns, define optional source branches.
CFR Part 11 compliance with digitally signed Pull Request Approvals.
Signees must approve with their username and password.
Require N digital signatures before a Pull Request can be merged.
Track signed off Pull Requests
Workzone for Bitbucket (Server) allows you to control your SCM workflow. It helps enterprises to implement their SCM process in a straightforward and intuitive way.
Predefined Pull Request Reviewers.
- Configure pre-defined (mandatory/suggested) reviewers and groups for branches, directories/files. A Pull Request will include these reviewers automatically.
- Replace Pull Request approvals with digital signatures
Automatic Pull Request Merge.
- Workzone merges a Pull Request automatically when all or a percentage of reviewers have approved or signed and/or on successful build results.
- Workzone can delete the source branch of a Pull Request after successful automatic merge.
- Require CFR Part 11 E-Signatures for Pull Request approvals
- Allow or block push operations to a branch once a Pull Request has been created and un-approve all approvals should the originating branch be updated.
- Block/Allow merging Pull Requests based on configurable merge conditions.
|10 users$10||25 users$100||50 users$200||100 users$500||250 users$1000||500 & upAdditional pricing details|
- How does server app pricing work?
Server products and apps are hosted on your servers. Licenses are perpetual and the purchase price include 12 months of maintenance (support and version updates).
You can renew maintenance after 12 months at 50% of the current purchase price. You can upgrade the tier of your host product and app licenses at any time. Upgrade prices are calculated based on Atlassian's formula (view example).
If app pricing changes after your initial purchase, there's a 60-day grandfathering period during which you can renew based on the old pricing.
- How do I determine my server pricing?
Apps are billed based on the number of users in your host product. The app tier should match the licensed user tier of the Atlassian host product. For example, if you have a Confluence Server license for 25 users, you should purchase the 25-user tier for apps. Even if fewer users want to use the app than your host product license, the two licenses should match exactly.
- Do you offer academic, community, or open-source licenses?
For server apps, purchase and renewal is half-price if you have an academic license for your Atlassian host product. Server apps are always free for community and open-source licenses.
For more details about qualifying for special licenses, see here.
- Can I extend my free trial?
For server apps, you can extend your app trial up to 5 times - in other words, for up to six months. Extend your trial by generating a new evaluation license key from Atlassian Marketplace. Click Try it free and you'll be directed to generate a new license. Paste this license key into the app listing in UPM from your Atlassian host product, and you're all set.
- How can I buy apps for my legacy Jira Server or Confluence Server license?
If you own a legacy Jira Server Unlimited (100+ users) or Confluence Server Unlimited (2000+ users) license purchased in 2012 or earlier, legacy app pricing is no longer available. You have two options for app purchasing:
- Purchase the app at the non-legacy Unlimited (10000+ users) tier.
- Renew your Jira or Confluence license at a non-legacy tier, then purchase the app at the same tier.
Izymes Pty Ltd is an Atlassian Verified vendor, committed to providing support for their apps at least 8 hours a day, 5 days a week.
Version 5.6.0 • Bitbucket Server 5.2.0 - 5.9.1 • Released 2018-02-07
Merge condition feature and UI improvements
Version 5.6.0 of Workzone features a new merge condition element
- Ignore contributor approvals for pull requests. Workzone will not count approvals from users that directly committed code for the pull request
Workzone now also has an improved (auto)-merge configuration UI.
- Log into your Bitbucket instance as an admin.
- Click the admin dropdown and choose Atlassian Marketplace. The Manage add-ons screen loads.
- Click Find new add-ons from the left-hand side of the page.
- Locate Workzone: PullRequest Workflow via search. The appropriate app version appears in the search results.
- Click Try free to begin a new trial or Buy now to purchase a license for Workzone: PullRequest Workflow. You're prompted to log into MyAtlassian. Workzone: PullRequest Workflow begins to download.
- Enter your information and click Generate license when redirected to MyAtlassian.
- Click Apply license. If you're using an older version of UPM, you can copy and paste the license into your Bitbucket instance.
To find older Workzone: PullRequest Workflow versions compatible with your instance, you can look through our version history page.