Advanced searching - development fields reference

Advanced searching

On this page

Related content

  • No related content found

Still need help?

The Atlassian Community is here for you.

Ask the community

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[builds].all

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

Syntax
development[builds].all
Field TypeTEXT
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 build:
    development[builds].all > 1

^ top of page

development[builds].passed

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

Syntax
development[builds].passed
Field TypeTEXT
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].passed > 1

^ top of page

development[builds].failing

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

Syntax
development[builds].failing
Field TypeTEXT
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 failing build:
    development[builds].failing > 1

^ top of page

development[builds].status

Search for issues that have builds in the specified status on a linked Bamboo instance or instances.

Syntax
development[builds].status = passed

development[builds].status = failed
Field TypeTEXT
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 failed builds:
    development[builds].status = failed

^ top of page

development[branches].all

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

Syntax
development[builds].all
Field TypeTEXT
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 branch:
    development[builds].failing > 1

^ 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 TypeTEXT
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 or not) on a linked Bitbucket instance or instances.

Syntax
development[deployments].all
Field TypeTEXT
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 deployments:
    development[deployments].all > 15

^ top of page

development[deployments].deployed

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

Syntax
development[deployments].deployed
Field TypeTEXT
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 which have been successfully deployed
    development[deployments].deployed > 0

^ 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 TypeTEXT
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 that have the test environment deployed
    development[deployments].environment = 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 TypeTEXT
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].open

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

Syntax
development[pullrequests].open
Field TypeTEXT
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].merged

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

Syntax
development[pullrequests].merged
Field TypeTEXT
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 merged pull requests:
    development[pullrequests].merged > 2

^ top of page

development[pullrequests].status

Search for issues with a specified status of the pull requests on a linked Bitbucket instance or instances.

Syntax
development[pullrequests].status = open

development[pullrequests].status = merged
Field TypeTEXT
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 merged pull requests:
    development[pullrequests].status = 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 TypeTEXT
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 TypeTEXT
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 Jun 19, 2020

Was this helpful?

Yes
No
Provide feedback about this article

Related content

  • No related content found
Powered by Confluence and Scroll Viewport.