GitHub Projects manual sort in one view is affected by sort settings in another view

[MakePixelsWork]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

Projects

Body

Description
In a GitHub Projects table, manual sorting in one view appears to be overridden or influenced by sorting configured in a different view/tab.

Addendum
I created my own columns for the issue number, in which I can sort the issues by their creation date, by their number. The sorting by number stated below is that custom column, but the bug still applies.

Steps to reproduce

1. Open a GitHub Project with multiple saved table views.
2. In View A, set:
   • Sort by: manual
   • Group by: none
   • optional filter: hide closed items
3. Manually reorder items in View A.
4. Open View B for the same project.
5. In View B, sort by Issue number.
6. Return to View A.

Expected behavior
Sorting in View B should affect only View B.
View A should preserve its own manual row order independently.

Actual behavior
After sorting View B by Issue number, View A no longer behaves like an independent manually ordered view. Its visible order appears affected by the sort used in View B. When the Issue number sort is removed in View B, View A returns to the expected manual ordering.

Additional details

• Group by: none
• Sort by: manual in the affected view
• Filter in use: hide closed items
• Show hierarchy: enabled when the issue was observed
• This makes view-level sorting appear to leak across tabs/views, even though sorting should be isolated per saved view.

Impact
This makes it difficult to maintain one view for manual prioritization and another for alternate sorts, because sorting in one tab can unexpectedly disrupt the manual order perceived in another.

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