Advanced searching - developer reference

There are a few ways to find issues depending on the state of your development efforts in linked products, for example, Bitbucket.

Source code specific searches

You can search for issues based on the your development status:

  • development[pullrequests].all (or .open) 
  • development[commits].all
  • development[reviews].all (or .open)
  • development[builds].failing


So for example if you wanted to find all your issues that have more than 2 failing builds you would use:

development[builds].failing > 2

Jira Software specific searches


Only applicable if Jira Software is installed and licensed and you have connected a build tool. Learn more about connecting Jira and Bitbucket.


Jira Software extends on this searching ability and adds the following search aliases:

Feature Flags

Alias Description Values available
flagEnabledRollout ~ for an enabled flag, how rolled out it is
  • "partial"

  • "full"

  • "zero"

flagDisabledRollout ~

how previously rolled out a currently disabled flag was
  • "true"

  • "full"

  • "zero"

flagEnabled ~ if the feature flag is enabled or not
  • "true"
  • "false"
flagName ~ shows feature flags with a specific name

"<name of flag>"

flagKey ~ shows feature flags with a specific key "<my flag key>"


Examples:

Show me all the issues that have a feature flag ON AND rollout is > 0% and < 100%:

flagEnabledRollout ~ “partial”


Show me all the issues that have a feature flag ON AND are at 100%:

flagEnabledRollout ~ “full”


Show me all the issues related to a flag that was rolled out to some people but is currently disabled:

flagDisabledRollout ~ "partial"


Show me issues connected to a feature flag called MakeEverythingBlue

flagName ~ “MakeEverythingBlue“

Deployments

Alias Description Values available
deploymentEnvironmentName ~ The name of your deployment environment "<my deployment name>"
deploymentEnvironmentType ~ The type of environment
  • “production“

  • “staging“

  • “testing“

  • “development“

  • “unmapped“

deploymentState ~ The current status of the deployment
  • “pending”

  • “in_progress”

  • “successful”

  • “cancelled”

  • “failed”

  • “rolled_back”

  • “unknown”

deploymentName ~

The name of the specific deployment "<my deployment name>"


Examples:

Show me all the issues that have been deployed to the prod-east or stg-west environments:

deploymentEnvironmentName ~ “prod-east“ OR deploymentEnvironmentName ~ “stg-west“


Show me all the issues on my board that have been deployed to production but still have an open PR:

deploymentEnvironmentType ~ “production“ AND development[pullrequests].open


Show me all the issues that have a feature flag ON AND at 100% AND are deployed to production:

flagEnabledRollout ~ “full“ AND deploymentEnvironmentType ~ “production“


Show me all the issues that have not been deployed to production:

deploymentEnvironmentType !~ “production“


Show me all issues that have been deployed to a prod-east, that have a feature flag on which is only partially rolled out:

deploymentEnvironmentName ~ “prod-east” AND flagEnabledRollout ~ “partial”


Builds

Alias Description Values available
buildState The status of a build reported by a cloud provider, for example, Bitbucket Pipelines
  • “pending“
  • “in progress“
  • “successful“
  • “failed“
  • “unknown“
buildName The name of a build reported by a cloud provider, for example, Bitbucket Pipelines "<My build name>"


Examples:

Show me all the issues where the latest build failed:

buildState ~ "failed"


Show me all the issues on my board that have an open pull request and the last build failed:

buildState ~ “FAILED“ AND development[pullrequests].open

Last modified on Feb 25, 2019

Was this helpful?

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