Steps to replicate the issue (include links if applicable):

• Sort the wish index page by any header.
• Go to a different page other than first page
• Sort again

What happens?:

• The wish index page is sorted by it does NOT go to first page

What should have happened instead?:

• The wish index page is sorted and it goes to the first page

---

Derived Requirement

Update the wish index table sorting behavior so that when a user changes the sorting order:

• The table should reset to the first page automatically.
• Sorting should correctly apply across all pages, not just the current one.
• Pagination state should only persist when navigating pages, not when changing the sort order.

Test Steps

Test Case 1: Sorting on First Page

1. Go to Wish Index.
2. On the first page, sort the table by a header (e.g., “Title”).
3. ✅❓❌⬜ AC1: Sorting is applied correctly and user remains on the first page (no unexpected navigation)..

Test Case 2: Sorting After Navigating to Another Page

1. Go to the Wish Index page.
2. Navigate to page 2 or beyond.
3. Sort the table by a header (e.g., “Status” or “Support Count”).
4. ✅❓❌⬜ AC2: Sorting is applied correctly and table automatically jumps back to page 1

Test Case 3: Sorting by Multiple Headers Sequentially

1. On the wish index, sort by “Title,” then sort by “Created.”
2. ✅❓❌⬜ AC3: Each sort correctly applies and after each sort, the user is on the first page

QA Results - Meta Beta