Cloud
Data Center 9.8
Versions

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 use even more parameters when performing a search. Adding development information to your JQL queries gives you more visibility of your development tools in Jira. So, you'll make better-informed decisions on your development and work, build a better, more reliable release pipeline, and deliver higher quality releases to your happy customers.

JQL is made up of clauses. In a clause, a field is followed by an operator. The operator is followed by one or more values or functions. The operator compares the value of the field on the left side with one or more values or functions on the right side. So, only valid results are retrieved by the clause. But you can't compare two fields in JQL.

To use development fields in your JQL queries, you can enter something like this when doing an advanced search:

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

This query will return all issues with the fix version 7.8.0 and open pull requests linked to them.

And what if you want to know how many builds are failing in your project? Try this query:

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

When using development fields for advanced search, you may see an error stating that the field doesn't exist or you don't have permission to view it. Learn more about this issue and how to resolve it in our knowledge base article.

Now, check the following development fields that can be used in JQL queries.

development[branches].all

Search for issues that have branches on Bitbucket instances.

Syntax
development[branches].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 two branches:
    development[branches].all > 2
  • Find all issues with at least one branch:
    development[branches].all > 0

^ top of page

development[builds].all

Search for issues that have builds on linked Bamboo 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 four builds:
    development[builds].all > 4
  • Find all issues with at least one build:
    development[builds].all > 0

^ top of page

development[builds].failing

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

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 three failing builds:
development[builds].failing > 3

^ top of page

development[builds].passing

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

Syntax
development[builds].passing
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 one passed build:
development[builds].passing > 1

^ top of page

development[builds].status

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

Syntax
development[builds].failing
Field TypeTEXT
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 builds:
    development[builds].status in (passed)
  • Find all issues with only failed builds:
    development[builds].status in (failed)
  • Find all issues with any information on builds:
    development[builds].status in (failed, passed)

^ top of page

development[commits].all

Search for issues that have code commits on linked Bitbucket 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
  • Find all issues with at least one commit:
    development[commits].all > 0

^ top of page

development[deployments].all

Search for issues that have successful and unsuccessful deployments on Bamboo 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 less than ten deployments:
    development[deployments].all < 10
  • Find all issues with at least one deployment:
    development[deployments].all > 0

^ top of page

development[deployments].deployed

Search for issues that have successful deployments on linked Bamboo 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 with more than two successful deployments:
development[deployments].deployed > 2

^ top of page

development[deployments].environment

Search for issues that have deployments to a specific environment on linked Bamboo instances. The supported environment functions are set in the Bamboo instances by the instance admin and can vary.

Syntax
development[deployments].environment
Field TypeTEXT
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 set in the Bamboo instances by the instance admin 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 linked Bitbucket 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 five open or merged pull requests:
    development[pullrequests].all > 5
  • Find all issues with at least one pull request:
    development[pullrequests].all > 0

^ top of page

development[pullrequests].declined

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

Syntax
development[pullrequests].declined
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 three declined pull requests:
development[pullrequests].declined > 3

^ top of page

development[pullrequests].merged

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

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 five merged pull requests:
development[pullrequests].merged > 5

^ top of page

development[pullrequests].open

Search for issues that have open pull requests on linked Bitbucket 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 two open pull requests:
development[pullrequests].open > 2

^ top of page

development[pullrequests].status

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

Syntax
development[pullrequests].status
Field TypeTEXT
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 linked Crucible 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 two open or closed reviews:
    development[reviews].all > 2
  • Find all issues with at least one review:
    development[reviews].all > 0

^ top of page

development[reviews].open

Search for issues that have open reviews on linked Crucible 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[reviews].open > 0

^ top of page

Last modified on Dec 13, 2022

Was this helpful?

Yes
No
Provide feedback about this article

Related content

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