Implied "in:title" missing from links in project workflow

[ezio-melotti]

Select Topic Area

Bug

Feature Area

Projects

Body

I tried enabling the Auto-add to projects workflow, using this query:

When I saved the workflow I got the following error:

I then removed the in:title from the query:

As you can see, the number of matches in the link under the query didn't change, stating that there are 7 matches. This leads me to think that the in:title is (now?) implied in the query, however when I click on the "See 7 existing items that match this query" link, the linked page shows a list of 50 matching issues, since the query in the link doesn't include the (possibly implied) in:title.

If the in:title is now implied, the link should be updated accordingly to contain it.

For reference, there are currently 7 open issues that match sqlite3 in:title (so the 7 in the "See 7 existing items" is correct), and 50 that match sqlite3.

---

As a side note, it's not clear what "new or updated item" exactly means -- I added a message on one of the matching issues (so I updated it), but the issue didn't get added to the project.

The docs don't clarify whether the in:title is implied nor the exact meaning of "updated".

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. ⭐