Add equivalent for Shift+G and P shortcuts in New Expensify

[twisterdotcom]

Overview

Expensify Classic supports keyboard shortcuts Shift+G and Shift+P. These should be implemented in the new App to maintain feature parity as an existing customer has asked for them.

Current Behavior

Keyboard shortcuts Shift+G and Shift+P are not available in the new Expensify App.

Expected Behavior

• Shift+G – Prompts the user for a Report ID and navigates directly to that report's page (quick-jump by report ID).
• Shift+P – When on a report page, navigates to the workspace/policy associated with that report.

As discussed in Slack, we will change these for New Expensify to:

• CMD+U - Opens the cmd+k switcher with type:expense-report reportid: entered waiting for the report ID
• CMD+B - Opens the workspace overview when viewing an expense report linked to that workspace

Platform

• Web
• Desktop
• iOS
• Android

Notes

1. These shortcuts exist in Expensify Classic (keyboardShortcutsDialogMainViewTemplate.html in Web-Expensify) and should be supported in the new App for users who rely on keyboard-driven navigation.
2. CMD = Ctrl in Windows
3. CMD was chosen over Shift as there are a lot more compose boxes you would not be able to use Shift+ reliably in New Expensify and U and B aren't yet taken by the browser natively.
4. If users are desperate to return to Shift+ shortcuts, we can come back to this, or we can encourage using some remapping key software internally.
5. Whilst CMD+U will not directly open the report, it will get there quicker.

Slack: https://expensify.slack.com/archives/C03U7DCU4/p1780048986882969

[melvin-bot]

Triggered auto assignment to Design team member for new feature review - @shawnborton (NewFeature)

[shawnborton]

Do we ever plan to support keyboard shortcuts for markdown? If so, these would collide badly (underline and bold).

[iwiznia]

Do we ever plan to support keyboard shortcuts for markdown? If so, these would collide badly (underline and bold).

🤷 I don't know honestly. I can change the keys to whatever we want...

[shawnborton]

Yeah, just a consideration but I don't feel strongly.

[nlemma]

Deploy Blocker #92810 was identified to be related to the PR #92064 that attempted to fix this issue.

[mitarachim]

Deploy Blocker #92813 was identified to be related to the PR #92064 that attempted to fix this issue.

[mitarachim]

Deploy Blocker #92815 was identified to be related to the PR #92064 that attempted to fix this issue.

[melvin-bot]

⚠️ Looks like this issue was linked to a Deploy Blocker here

If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.

If a regression has occurred and you are the assigned CM follow the instructions here.

If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.

[jponikarchuk]

Deploy Blocker #92825 was identified to be related to the PR #92064 that attempted to fix this issue.