Filter logic for "-assignee" removes tasks with multiple assignees

[sarun-r]

Select Topic Area

Product Feedback

Feature Area

Projects

Body

The current behavior of the -assignee filter in GitHub Projects and issue searches is problematic when an issue has multiple assignees.

The Problem:

When a single issue is assigned to two users (e.g., user-A and user-B), a search query to exclude one of them using -assignee removes the issue from the view for both users.

For example, a project manager and a designer are assigned to a single issue. The designer wants to see all their tasks but exclude the ones the project manager is also assigned to.

Reproduction Steps:

Create a new issue.

Assign the issue to two users, user-A and user-B.

Go to the search bar and enter the filter: assignee:user-A -assignee:user-B

Expected Behavior:

The issue should appear in the search results because it is assigned to user-A.

Actual Behavior:

The issue is filtered out and does not appear in the search results.

This behavior makes it impossible to create a filtered view for a single user on issues that are also shared with a second user, which is a common scenario in project management. A more useful logic would be for -assignee to exclude only the specified user's involvement, not the entire issue from the results.

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