You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
We have a common problem - too many pull requests in too many repositories and projects all at the same time! Here are three easy ways to organize and structure all pull requests across your entire Bitbucket instance.
Just like for Jira issues or Github pull requests, labels have their place in Bitbucket (we believe)! Labels help to categorize and structure pull requests in a really simple and straightforward manner.
To help you organize your sprints and release cycles, due-dates for pull requests are a must. They serve as a reminder for what to focus on this week, or which pull requests need to be merged today.
With labelled pull requests plus due-dates you can search the entire instance with what we like to call Bitbucket Query Language (BQL) like:
label in (important, release) & duedate <= today() & state = open
Labels and due-dates are essential to prioritize your daily work.
Pull request overwhelm ends right here!
Break the chains of viewing pull request lists only inside repositories. Organizr filters and lists all pull requests across your entire Bitbucket instance.
We have pull request labels and due-dates to bring more structure. However, if that's not enough, Organizr adds even more search vectors such as reviewer names, authors, target branches and projects.
But what if you're looking for something less structured like a few keywords in the pull request title or description? Organizr will find pull requests based on any words in the title or description text. Looking for all pull requests that deal with 'vulnerabilities' or 'vulnerability'? Just BQL-search with:
text = vulnerability
In real life everyone wants their tasks in order and prioritized, and it's no different with pull requests in Bitbucket!
When it comes to getting the next release out and deployed - more often than not things don’t go as smooth as you wish. There’s a last-minute bugfix and another feature just got finished, plus there is that bug in production that needs to be fixed immediately.
Organizr structured merge hierarchy enables your team to prioritize and structure pull requests across repositories, projects and the entire Bitbucket instance. Create a dependency tree via drag and drop to ensure that pull requests are merged in order.
Organizr for Data Centre is available on the Atlassian Marketplace.
Happy coding and organizing!
Ulrich, Izymes Founder
Izymes’ mission is to eliminate boring from work. We build apps that turbo-charge team velocity through contextual automation.