Support & Downloads

Izymes builds easy-to-use apps for Atlassian applications that boost your productivity, free you from performing repetitive tasks inside Confluence, Jira and Bitbucket and enable you to use your time for what you do best – YOUR job.

Book a Demo

Interested in a 1-on-1 demonstration of Izymes’s products?
Here we will walk you through;

• All features and benefits of the product you are interested in trying.
• How to set up the account and configure the settings.
• Other tips, tricks and best practices.

It will also give us time to answer any questions you may have, or perhaps you just want to have a chat, we love a good chat.
You can schedule a time on the Calendly link below. Talk soon!

Contact Info
HQ Southport
Queensland, Australia
[email protected]
Follow Us
View Categories

Filter Pull Requests across the entire instance

Get rid of the shackles of viewing Pull Request lists only inside repositories. Organizr filters and lists all Pull Requests across the entire Bitbucket instance. Filter by due date, label(s), author, reviewer, state …

You can choose to filter through boolean search string or select options from the dropdown options, such as Label, Author, Reviewer etc.

Query semantics & operators
Organizr supports a structured filter query syntax with the following operator rules:

  • & means AND (all conditions must match).
  • There is no OR operator (no |).
  • = requires the PR to match all values provided (combined match).
    • Example: reviewer = (usera, userb) returns PRs that have both usera and userb as reviewers.
    • Example: label = (urgent, release) returns PRs that have both labels applied.
  • IN matches any value in the list (either/or match).
    • Example: reviewer IN (usera, userb) returns PRs that have either usera or userb as a reviewer.
    • Example: label IN (urgent, release) returns PRs that have either label applied.
  • Use quotes for values containing spaces or special characters (e.g., text = "annoying client").

UI behavior (selectors):
The Organizr UI selectors always compile multi-selections using IN (because this is usually what users expect). If you need a combined match (e.g., PRs that contain all selected reviewers/labels), you can manually edit the query and change IN to = for that clause.

Common gotcha (reviewers/labels):

  • Use IN when you mean “any of these reviewers/labels”.
  • Use = when you mean “must contain all of these reviewers/labels”.
Try Organizr!