Skip to content

[Due for payment 2026-07-03] Add equivalent for Shift+G and P shortcuts in New Expensify #92247

Closed

Description

@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

Issue OwnerCurrent Issue Owner: @mallenexpensify

Activity

  1. melvin-bot commented on Jun 1, 2026

    @melvin-bot

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

  2. shawnborton commented on Jun 1, 2026

    @shawnborton
    Contributor

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

  3. iwiznia commented on Jun 1, 2026

    @iwiznia
    Contributor

    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...

  4. shawnborton commented on Jun 1, 2026

    @shawnborton
    Contributor

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

  5. nlemma commented on Jun 5, 2026

    @nlemma

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

  6. mitarachim commented on Jun 5, 2026

    @mitarachim

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

  7. mitarachim commented on Jun 5, 2026

    @mitarachim

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

  8. melvin-bot commented on Jun 5, 2026

    @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.

  9. jponikarchuk commented on Jun 5, 2026

    @jponikarchuk

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

  10. nlemma commented on Jun 5, 2026

    @nlemma

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

  11. 20 remaining items

  12. melvin-bot commented on Jul 1, 2026

    @melvin-bot

    @truph01 Huh... This is 4 days overdue. Who can take care of this?

  13. melvin-bot commented on Jul 2, 2026

    @melvin-bot

    Triggered auto assignment to @mallenexpensify (Awaiting Payment)

  14. melvin-bot commented on Jul 2, 2026

    @melvin-bot

    Payment Summary

    Upwork Job

    • Reviewer: @truph01 owed $250 via NewDot

    BugZero Checklist (@mallenexpensify)

    • I have verified the correct assignees and roles are listed above and updated the necessary manual offers
    • I have verified that there are no duplicate or incorrect contracts on Upwork for this job (https://www.upwork.com/ab/applicants//hired)
    • I have verified the PR was not reverted
    • I have applied any discounts due to bugs/regressions introduced by this PR
    • I have paid out the Upwork contracts or cancelled the ones that are incorrect
    • I have verified the payment summary above is correct
  15. mallenexpensify commented on Jul 6, 2026

    @mallenexpensify
    Contributor

    Payment Summary

    Contributor+: @truph01 due $250 via NewDot

    Not taking into account regressions cuz it doesn't look/sound like @truph01 should have caught them (and they worked on fixing them). Comment if you disagree.

    ^ Test case created. Thx

  16. truph01 commented on Jul 7, 2026

    @truph01
    Contributor

    @mallenexpensify, it looks like there are two payment summaries: #92247 (comment) & #92992 (comment).

    We should have only one.

  17. mallenexpensify commented on Jul 7, 2026

    @mallenexpensify
    Contributor

    Thanks @truph01 , removed other payment summary and left comment on that issue

  18. garrettmknight commented on Oct 12, 2026

    @garrettmknight
    Contributor

    $250 approved for @truph01

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionDailyKSv2NewFeatureSomething to build that is a new item.

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions