Skip to content

az pipelines list non-intuitive behavior when using --query-order #26254

Description

@ms-markcoppa

Given an Azure ADO project with pipelines. Some of the pipelines are in the root folder. Other pipelines exist in folders and sub-folders.

In this situation, calling az pipelines list returns more results if providing --query-order. For example:

returns 1,256 recrords
az pipelines list --org [org] --project [project]

returns 1,472 records
az pipelines list --org [org] --project [project] --query-order NameAsc

Expected behavior is that both commands should return the same set of records, albeit in a different order. If the current behavior is by design, then this should be documented.


Document Details

Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Auto-AssignAuto assign by botDevOpsPipelinesService AttentionThis issue is responsible by Azure service team.act-platform-engineering-squadbugThis issue requires a change to an existing behavior in the product in order to be resolved.

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions