Filters similar to iteration:<@keyword have a warning

[Hannnes1]

Select Topic Area

Bug

Feature Area

Projects

Body

Starting today, one of our filters in a project shows a warning that it is invalid.

The filter looks like this: -sprint:<@current-2 and the warning is:

Filter contains 1 issue:

Invalid value `<@current-2` for `-sprint`

Simplifying the filter to sprint:<@current also shows a similar warning.

Despite that it seems like the filter still works as intended, so the warning is only annoying.

Guidelines

• I have read the above statement and can confirm my post is relevant to the GitHub feature areas Issues and/or Projects.

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[FaronBracy]

Same thing started happening today for us with a filter pi:>=@current -sprint:<@current

Started to see this warning:

Filter contains 2 issues:

    Invalid value `>=@current` for `pi`
    Invalid value `<@current` for `-sprint`

Although the warning is displayed, the filter seems to continue working as expected.

[ColtonBehannon]

I thought there would be some update or fix by now, but I haven't seen anything yet. This is an issue across all of my boards.

[rileybroughten]

Thank you all for the reports - we just pushed a fix for this. Could you confirm you are no longer seeing the errors?

[Hannnes1]

Can confirm!

[FaronBracy]

Can confirm here too

[ColtonBehannon]

I am still seeing the issue. What I see is:

Filter contains 1 issue:
Invalid value "Sprint*" for status

[rileybroughten]

@ColtonBehannon could you share the filter you are using so we can investigate?

[ColtonBehannon]

Sure thing.

status:"Sprint*" sprint:@current