• [转]Advanced search reference JQL developer status


    本文转自:https://support.atlassian.com/jira-software-cloud/docs/advanced-search-reference-jql-developer-status/

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

    Before you begin

    The content on this page applies only if you have Jira Software Cloud connected to a build tool. Learn more about connecting Jira and Bitbucket.

    Source code 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

    Feature Flags

    AliasDescriptionValues 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

     

    Note that these do not work for Bamboo deployments

    AliasDescriptionValues 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

    AliasDescriptionValues 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

  • 相关阅读:
    Rest API
    Spring webflux
    混合配置
    Profile
    Bean的作用域
    事件的监听与发布
    Condition
    完美解决 fatal: unable to access ‘https://github.com/.../.git‘: Could not resolve host: github.com
    virtualbox 给centos扩容方法
    Mac 安装mysqlclient报错 OSError: mysql_config not found
  • 原文地址:https://www.cnblogs.com/freeliver54/p/15876928.html
Copyright © 2020-2023  润新知