Advanced searching - development fields reference

If you've linked your development tools to Jira, you can now search by even more parameters when performing a search. Adding development information to your JQL gives you more visibility of your development tools in one place, Jira. This lets you make better informed decisions on your development and work, helps you build a better, more reliable release pipeline, and ensures you deliver higher quality releases to your happy customers.

JQL is made up of clauses, and in a clause, a field is followed by an operator, which in turn is followed by one or more values (or functions). The operator compares the value of the field with one or more values or functions on the right, such that only true results are retrieved by the clause.

To use development fields in your JQL, you would enter something like this in an advanced search:

fixVersion = 7.8.0 AND development[pullrequests].open > 0

This would return all issues with a fix version of 7.8.0, and that have open pull requests linked to them. How about how many builds are failing in your project? Try:

project = ABC AND development[builds].failing > 0

The following development fields can be used in JQL:

development[branches].all

Search for issues that have branches on a linked Bitbucket instance or instances.

Syntax
development[branches].all
Field Type TEXT
Auto-complete

No

Supported operators

= , != , > , >= , < , <=

Unsupported operators ~ , !~, IS , IS NOT , IN , NOT IN,
WAS, WAS IN, WAS NOT, WAS NOT IN, CHANGED
Supported functions

None

Examples
  • Find all issues with more than 2 branches:
    development[branches].all > 2

^ top of page

development[builds].all

Search for issues that have builds on a linked Bamboo instance or instances.

Syntax
development[builds].all
Field Type TEXT
Auto-complete

No

Supported operators

= , != , > , >= , < , <=

Unsupported operators ~ , !~, IS , IS NOT , IN , NOT IN,
WAS, WAS IN, WAS NOT, WAS NOT IN, CHANGED
Supported functions

None

Examples
  • Find all issues with more than 4 builds:
    development[builds].all > 4

^ top of page

development[builds].failing

Search for issues that have failed builds on a linked Bamboo instance or instances. Note that the issues may also have passed builds associated with them, so ensure to build your JQL query to exclude passed builds if that's what you require.

Syntax
development[builds].failing
Field Type TEXT
Auto-complete

No

Supported operators

= , != , > , >= , < , <=

Unsupported operators ~ , !~, IS , IS NOT , IN , NOT IN,
WAS, WAS IN, WAS NOT, WAS NOT IN, CHANGED
Supported functions

None

Examples
  • Find all issues with more than 3 failing builds:
    development[builds].failing > 3

^ top of page

development[builds].passing

Search for issues that have passed builds on a linked Bamboo instance or instances. Note that the issues may also have failed builds associated with them, so ensure to build your JQL query to exclude failed builds if that's what you require.

Syntax
development[builds].passing
Field Type TEXT
Auto-complete

No

Supported operators

= , != , > , >= , < , <=

Unsupported operators ~ , !~, IS , IS NOT , IN , NOT IN,
WAS, WAS IN, WAS NOT, WAS NOT IN, CHANGED
Supported functions

None

Examples
  • Find all issues with more than 1 passed build:
    development[builds].passing > 1

^ top of page

development[builds].status

Search for issues that have builds that have passed or failed on a linked Bamboo instance or instances.

Syntax
development[builds].failing
Field Type TEXT
Auto-complete

No

Supported operators

= , != , IN , NOT IN

Unsupported operators > , >= , < , <=, ~ , !~, IS , IS NOT ,
WAS, WAS IN, WAS NOT, WAS NOT IN, CHANGED
Supported functions

passed, failed

Examples
  • Find all issues with only passed build/s:
    development[builds].status in (passed)
  • Find all issues with only failed build/s:
    development[builds].status in (failed)
  • Find all issues with build information:
    development[builds].status in (failed, passed)

^ top of page

development[commits].all

Search for issues that have code commits on a linked Bitbucket instance or instances.

Syntax
development[commits].all
Field Type TEXT
Auto-complete

No

Supported operators

= , != , > , >= , < , <=

Unsupported operators ~ , !~, IS , IS NOT , IN , NOT IN,
WAS, WAS IN, WAS NOT, WAS NOT IN, CHANGED
Supported functions

None

Examples
  • Find all issues with more than 15 commits:
    development[commits].all > 15

^ top of page

development[deployments].all

Search for issues that have deployments (successful and unsuccessful) on a linked Bamboo instance or instances.

Syntax
development[deployments].all
Field Type TEXT
Auto-complete

No

Supported operators

= , != , > , >= , < , <=

Unsupported operators ~ , !~, IS , IS NOT , IN , NOT IN,
WAS, WAS IN, WAS NOT, WAS NOT IN, CHANGED
Supported functions

None

Examples
  • Find all issues with less than 10 deployments:
    development[deployments].all < 10

^ top of page

development[deployments].deployed

Search for issues that have successful deployments on a linked Bamboo instance or instances.

Syntax
development[deployments].deployed
Field Type TEXT
Auto-complete

No

Supported operators

= , != , > , >= , < , <=

Unsupported operators ~ , !~, IS , IS NOT , IN , NOT IN,
WAS, WAS IN, WAS NOT, WAS NOT IN, CHANGED
Supported functions

None

Examples
  • Find all issues with more than 2 successful deployments:
    development[deployments].deployed > 2

^ top of page

development[deployments].environment

Search for issues that have deployments to a specific environment on a linked Bamboo instance or instances. The supported environment functions are those set in the Bamboo instance/s. These are set by the administrator of the Bamboo instance, and can vary.

Syntax
development[deployments].environment
Field Type TEXT
Auto-complete

No

Supported operators

= , != , IN , NOT IN

Unsupported operators > , >= , < , <=, ~ , !~, IS , IS NOT ,
WAS, WAS IN, WAS NOT, WAS NOT IN, CHANGED
Supported functions

The supported environment functions are those set in the Bamboo instance/s. These are set by the administrator of the Bamboo instance, and can vary.

Examples
  • Find all issues with deployments to a production environment:
    development[deployments].environment in (production)
    development[deployments].environment = production

^ top of page

development[pullrequests].all

Search for issues that have open or merged pull requests on a linked Bitbucket instance or instances.

Syntax
development[pullrequests].all
Field Type TEXT
Auto-complete

No

Supported operators

= , != , > , >= , < , <=

Unsupported operators ~ , !~, IS , IS NOT , IN , NOT IN,
WAS, WAS IN, WAS NOT, WAS NOT IN, CHANGED
Supported functions

None

Examples
  • Find all issues with more than 5 open or merged pull requests:
    development[pullrequests].all > 5

^ top of page

development[pullrequests].declined

Search for issues that have declined pull requests on a linked Bitbucket instance or instances. Note that this will also return issues with merged pull requests.

Syntax
development[pullrequests].declined
Field Type TEXT
Auto-complete

No

Supported operators

= , != , > , >= , < , <=

Unsupported operators ~ , !~, IS , IS NOT , IN , NOT IN,
WAS, WAS IN, WAS NOT, WAS NOT IN, CHANGED
Supported functions

None

Examples
  • Find all issues with more than 3 declined pull requests:
    development[pullrequests].declined > 3

^ top of page

development[pullrequests].merged

Search for issues that have merged pull requests on a linked Bitbucket instance or instances. Note that this will also return issues with declined requests.

Syntax
development[pullrequests].merged
Field Type TEXT
Auto-complete

No

Supported operators

= , != , > , >= , < , <=

Unsupported operators ~ , !~, IS , IS NOT , IN , NOT IN,
WAS, WAS IN, WAS NOT, WAS NOT IN, CHANGED
Supported functions

None

Examples
  • Find all issues with more than 5 merged pull requests:
    development[pullrequests].merged > 5

^ top of page

development[pullrequests].open

Search for issues that have open pull requests on a linked Bitbucket instance or instances.

Syntax
development[pullrequests].open
Field Type TEXT
Auto-complete

No

Supported operators

= , != , > , >= , < , <=

Unsupported operators ~ , !~, IS , IS NOT , IN , NOT IN,
WAS, WAS IN, WAS NOT, WAS NOT IN, CHANGED
Supported functions

None

Examples
  • Find all issues with more than 2 open pull requests:
    development[pullrequests].open > 2

^ top of page

development[pullrequests].status

Search for issues that have an open and/or merged pull requests on a linked Bitbucket instance or instances.

Syntax
development[pullrequests].status
Field Type TEXT
Auto-complete

No

Supported operators

= , != , IN , NOT IN

Unsupported operators > , >= , < , <= , ~ , !~, IS , IS NOT ,
WAS, WAS IN, WAS NOT, WAS NOT IN, CHANGED
Supported functions

None

Examples
  • Find all issues with open pull requests:
    development[pullrequests].status = open
    development[pullrequests].status in (open)
  • Find all issues with open and merged pull requests:
    development[pullrequests].status in (open,merged)

^ top of page

development[reviews].all

Search for issues that have open or closed reviews on a linked Crucible instance or instances.

Syntax
development[reviews].all
Field Type TEXT
Auto-complete

No

Supported operators

= , != , > , >= , < , <=

Unsupported operators ~ , !~, IS , IS NOT , IN , NOT IN,
WAS, WAS IN, WAS NOT, WAS NOT IN, CHANGED
Supported functions

None

Examples
  • Find all issues with more than 2 open or closed reviews:
    development[review].all > 2

^ top of page

development[reviews].open

Search for issues that have open reviews on a linked Crucible instance or instances.

Syntax
development[reviews].open
Field Type TEXT
Auto-complete

No

Supported operators

= , != , > , >= , < , <=

Unsupported operators ~ , !~, IS , IS NOT , IN , NOT IN,
WAS, WAS IN, WAS NOT, WAS NOT IN, CHANGED
Supported functions

None

Examples
  • Find all issues with open reviews:
    development[review].open > 0

^ top of page

Last modified on Aug 23, 2019

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.