Feature: Enhance Activity Streams with descending sorting and pagination #670
Description
Summary
This feature request is about enhancing the behaviour of Activity Stream sections on the Candidate, Company and Contact screen.
The goal is to make all Activity Streams easier to read and navigate by:
- always showing the most recent activities at the top, and
- introducing pagination
This proposal is related to, but independent from, the feature request #669.
Current behavior
- Activity sections on entity screens (Candidates, Contacts and Companies) can grow very long over time.
- Older activities can appear at the top of the list, while recent entries are further down, making it harder to see "what’s going on right now" at a glance.
- There is no per-screen pagination on these Activity Streams, which can lead to very long, scroll-heavy pages for entities with a long history of interactions.
- There already is some pagination available on the global Activities module.
Expected behavior
Apply the following consistent behaviour to all Activity Streams on:
- Candidate screen
- Company screen (company-level Activity Stream, once implemented – see Feature: Consolidated contact activity stream on Company screen #669)
- Contact screen
1. Sorting
- Default sort order: descending by activity date/time (newest activities at the top).
2. Pagination
- Introduce pagination for each Activity Stream.
- Provide a simple “Rows per page” selector (following the pattern already used in the global Activities screen).
Motivation / Use cases
- See what’s current, first: Users typically care most about the latest calls, emails, and notes. Showing the most recent items first avoids having to scroll past years-old activities.
- Better readability for busy records: Some Companies, Contacts, and Candidates accumulate a lot of history. Pagination keeps the page usable and avoids excessively long, scroll-heavy screens.
- Consistent UX across the system: The global Activities screen already has pagination and configurable rows per page. Applying similar behaviour to entity-level Activity Streams makes the system feel more consistent and predictable.
- Performance considerations: Limiting the number of rows per page can improve perceived performance on large datasets, especially when activity history grows over time.