[Due for payment 2025-06-12] [Due for payment 2025-06-11] Add keyboard shortcut for "mark all as read"

[JmillsExpensify]

Per Slack convo, despite our best efforts, we still commonly run into situations where someone ends up with more unreads than they want. For instance:

• Their account is migrated, yet they continue to use OldDot
• We create bugs, don't change the lastReadTime

And more, again those are just examples. In any case, we'd like to give support the ability to help users in this situation, and also let users discover this themselves by referring to our keyboard shortcut legend. As a result we want to:

1. Add a new keyboard shortcut, Shift + Esc, that sets a historical lastReadTime to the current time, which effectively marks it as read.

2. Update https://new.expensify.com/keyboard-shortcuts with the new shortcut to make it discoverable by anyone

cc @heyjennahay @puneetlath from Slack

Issue Owner

Current Issue Owner: @

Issue Owner

Current Issue Owner: @jliexpensify

[melvin-bot]

Triggered auto assignment to Contributor-plus team member for initial proposal review - @s77rt (External)

[melvin-bot]

Triggered auto assignment to @jliexpensify (NewFeature), see https://stackoverflowteams.com/c/expensify/questions/14418#:~:text=BugZero%20process%20steps%20for%20feature%20requests for more details. Please add this Feature request to a GH project, as outlined in the SO.

[truph01]

Proposal

Please re-state the problem that we are trying to solve in this issue.

• Add a keyboard shortcut for the "Mark All as Read" functionality to improve usability and accessibility.

What is the root cause of that problem?

• This is a new feature request; the functionality does not yet exist.

What changes do you think we should make in order to solve the problem?

1. Define a new keyboard shortcut configuration for "Mark All as Read". The actual shortcut key should be chosen based on team consensus:

MARK_AS_READ: {
    descriptionKey: 'markAsRead',
    shortcutKey: '', // e.g., 'M'
    modifiers: ['CTRL', 'SHIFT'],
    trigger: {},
},

2. In AuthScreens.tsx, subscribe to the new shortcut:

const markAsReadShortcutConfig = CONST.KEYBOARD_SHORTCUTS.MARK_AS_READ;
const unsubscribeMarkAsRead = KeyboardShortcut.subscribe(
    markAsReadShortcutConfig.shortcutKey,
    markAllAsRead, // Defined in step 3
    markAsReadShortcutConfig.descriptionKey,
    markAsReadShortcutConfig.modifiers,
    true,
);

3. Implement the markAllAsRead callback function. There are two possible implementations:

Option A – Mark the topmost report as read:

const markAllAsRead = useCallback(() => {
    Report.readNewestAction(Navigation.getTopmostReportId());
}, []);

Option B – Mark all unread reports as read:

const [allReports] = useOnyx(ONYXKEYS.COLLECTION.REPORT, {canBeMissing: true});
const [allReportActions] = useOnyx(ONYXKEYS.COLLECTION.REPORT_ACTIONS, {canBeMissing: true});
const markAllAsRead = useCallback(() => {
    let delay = 0;
    Object.keys(allReports ?? {}).forEach((key: string) => {
        const report = allReports?.[key];
        const oneTransactionThreadReportID = getOneTransactionThreadReportID(
            report?.reportID,
            allReportActions?.[`${ONYXKEYS.COLLECTION.REPORT_ACTIONS}${report?.reportID}`]
        );
        const oneTransactionThreadReport = allReports?.[`${ONYXKEYS.COLLECTION.REPORT}${oneTransactionThreadReportID}`];

        if (!isUnread(report, oneTransactionThreadReport)) {
            return;
        }

        setTimeout(() => {
            Report.readNewestAction(report?.reportID);
        }, delay);

        delay += 1000;
    });
}, []);

We can choose the appropriate implementation depending on performance considerations and the intended user experience.

What specific scenarios should we cover in automated tests to prevent reintroducing this issue in the future?

• None

What alternative solutions did you explore? (Optional)