Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Only the default condition on Task Instance filters work #34313

Closed
1 of 2 tasks
LiamOrmiston opened this issue Sep 12, 2023 · 1 comment
Closed
1 of 2 tasks

Only the default condition on Task Instance filters work #34313

LiamOrmiston opened this issue Sep 12, 2023 · 1 comment
Labels
area:core duplicate Issue that is duplicated kind:bug This is a clearly a bug

Comments

@LiamOrmiston
Copy link
Contributor

Apache Airflow version

Other Airflow 2 version (please specify below)

What happened

On version 2.7.0
When adding filters to the Browse -> Task Instances page, only the default condition on any filter works. This is either Starts with or Equal to depending on the filter.

For example:
When adding a Task Id filter, only the Starts with condition works. Picking Ends with will result in a search as if you never entered that filter at all. The filter will not appear under the search drop down and the results do not reflect that the filter was applied.

Adding Starts with and Ends with results in just Starts with being applied.

What you think should happen instead

Each condition should work on any given filter.

How to reproduce

  1. Go to the Browse -> Task Instances page
  2. Select the Search drop down
  3. Pick any filter
  4. Change the conditon to something other than the default choice
  5. Add something to the condition field
  6. Hit Search

Operating System

CentOS Stream 8

Versions of Apache Airflow Providers

No response

Deployment

Official Apache Airflow Helm Chart

Deployment details

No response

Anything else

No response

Are you willing to submit PR?

  • Yes I am willing to submit a PR!

Code of Conduct

@LiamOrmiston LiamOrmiston added area:core kind:bug This is a clearly a bug needs-triage label for new issues that we didn't triage yet labels Sep 12, 2023
@SamWheating
Copy link
Contributor

I believe that this is the same issue reported in #33895 which was fixed in #33931, which was included in the 2.7.1 release.

@Taragolis Taragolis added duplicate Issue that is duplicated and removed needs-triage label for new issues that we didn't triage yet labels Sep 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:core duplicate Issue that is duplicated kind:bug This is a clearly a bug
Projects
None yet
Development

No branches or pull requests

3 participants