# Feature OP-20003 - Next / previous navigation through a filtered set

Project: OpenProject
Status: new
URL: https://community.openproject.org/work_packages/OP-20003

## Planning

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | Medium |
| Target versions | Wish List |
| Sprint |  |
| Backlog bucket |  |
| Votes | 1 |
| List |  |
| Roadmap |  |
| Relevance |  |

## OPEN POINTS / FEEDBACK

_No work packages_

## Features and Chunks

_No work packages_

## Bugs and other work packages

_No work packages_

## Technical Details

| Attribute | Value |
| --- | --- |
| Module | Modules and project features / Work packages, Modules and project features / Query and filter, Frontend components and Primer design system |
| Feature Flag |  |
| Requires doc change | No |
| Enterprise plan |  |

## Details

| Attribute | Value |
| --- | --- |
| Pull preview |  |
| Mockups |  |
| Accessibility | No |

## People

| Attribute | Value |
| --- | --- |
| Assignee |  |
| Accountable |  |
| Product manager |  |
| Feature Lead |  |
| Developers |  |
| Designer |  |
| Ordered by |  |
| Signed off by |  |
| Interest by |  |

## Estimates and progress

| Attribute | Value |
| --- | --- |
| PD (min) |  |
| PD (max) |  |
| Work |  |
| Labor costs |  |

## Description

**As a** reviewer working through a filtered set of work packages,
**I want** to move to the next or previous work package in the active query directly from the full-screen work package view,
**so that** I can walk through the filtered set one case at a time, in full, without returning to the table between each one.

**Acceptance criteria**

* When I open a work package from a filtered table, the full-screen view retains the query context (the active filters **and** sort order).
* The full-screen view shows clickable **Previous** and **Next** controls that move to the adjacent work package in the query's result order.
* The sequence produced by Previous/Next matches the table order exactly, honouring the current sort and filters.
* A position indicator is shown, e.g. "12 of 87".
* Previous/Next are disabled (or clearly marked as the end) at the first and last item of the set.
* After paging through cases, returning to the table lands me back in the same filtered/sorted list, at or near where I was.
* Keyboard shortcuts for previous/next are available alongside the clickable controls (e.g. extending `j`/`k` or arrow keys to the full view). *Nice-to-have — the customer stated clickable controls alone are sufficient.*

**Technical notes**

* The query (filters + sort) is already a first-class concept; the gap is that the full-screen route does not carry the ordered result set. Passing the query into the full view and resolving the neighbouring work package id from the ordered results would drive the controls.
* `j`/`k` currently apply to lists only per the keyboard-shortcuts docs; this may be a natural place to extend them.

**Out of scope**

* Navigation across work packages that are not part of the active query (e.g. global next/previous irrespective of filter).
    

_Set the_ **To be informed/consulted teams** _field to include all teams necessary to be informed of the changes._
