Unable to filter the pipeline execution with multiple custom tags
long-term
A
Aquamarine Tyrannosaurus
We have multiple custom tags defined for pipelines and when we search executions using multiple tags using filters it is not working as expected. It is working as expected when we filter with single tag.
We need help to filter with AND condition for tags filter.
Log In
Canny AI
Merged in a post:
Support AND Logic for Filtering Pipelines by Multiple Tags
E
Exceptional Mole
Description:
Currently, Harness applies the following search logic for filtering pipelines:
Name and Tags Fields: AND logic is applied between the Name and Tags fields.
Tags Only: OR logic is used when filtering pipelines using multiple tags.
Customer Request:
Customers have expressed the need for an AND logic when filtering pipelines by multiple tags. This would allow them to narrow down results more effectively, displaying only those pipelines that match all specified tags simultaneously.
Use Case:
This enhancement will be particularly useful for organizations with a large number of pipelines, where granular filtering is essential to identify pipelines with specific combinations of tags.
Canny AI
Merged in a post:
Executions API should allow filtering by multiple tags with AND logic.
N
Nickel Reindeer
This API to get executions has a pipelineTags filter:
..but it applies multiple tag filters with OR logic. This is counterintuitive since all the other filter options such as pipelineId, searchTerm, and status are combined with AND logic.
It would be a breaking change to simply change it, but could some way be provided to allow filtering on multiple tags with AND logic?
- Maybe a new property like pipelineTagsAll.
- Or perhaps if the current array of objects is sent it's ORed...
[
{ "key": "Build-Type": "value: "branch"},
{ "key": "Build-Type": "value: "PR"},
]
...but if it's an object they are ANDed:
{
"Build-Type": "branch",
"Approved": "true"
}
Prasad Satam
long-term
Thanks for the feedback! This enhancement request has been given top priority and is now officially in our development pipeline!
We will keep you updated on the progress and let you know as soon as it is available.
Should you have any questions, suggestions, or thoughts you'd like to share, please feel free to add more to this feature request.