Skip to content

[PAID] Report - No Export to [Accounting system] primary option on paid report #61092

Closed

Description

@lanitochka17

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!


Version Number: 9.1.33-7
Reproducible in staging?: Y
Reproducible in production?: N
If this was caught during regression testing, add the test name, ID and link from TestRail: #59999
Issue reported by: Applause - Internal Team

Action Performed:

Prerequisites: Have a workspace connected to an accounting system

  1. Go to staging.new.expensify.com
  2. Create new expense report in workspace with accounting
  3. Submit the report
  4. Approve report
  5. Pay the report

Expected Result:

After report is payed there is Export to [Accounting system] primary option

Actual Result:

After report is payed there is no Export to [Accounting system] primary option

Workaround:

Unknown

Platforms:

Select the officially supported platforms where the issue was reproduced:

  • Android: App
  • Android: mWeb Chrome
  • iOS: App
  • iOS: mWeb Safari
  • iOS: mWeb Chrome
  • Windows: Chrome
  • MacOS: Chrome / Safari
  • MacOS: Desktop
Platforms Tested: On which of our officially supported platforms was this issue tested:
  • Android: App
  • Android: mWeb Chrome
  • iOS: App
  • iOS: mWeb Safari
  • iOS: mWeb Chrome
  • Windows: Chrome
  • MacOS: Chrome / Safari
  • MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence
Bug6816623_1745943339906.Recording__312.mp4

View all open jobs on GitHub

Issue OwnerCurrent Issue Owner: @strepanier03

Activity

  1. melvin-bot commented on Apr 29, 2025

    @melvin-bot

    Triggered auto assignment to @carlosmiceli (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

  2. github-actions commented on Apr 29, 2025

    @github-actions
    Contributor

    👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:

    1. Identify the pull request that introduced this issue and revert it.
    2. Find someone who can quickly fix the issue.
    3. Fix the issue yourself.
  3. melvin-bot commented on Apr 29, 2025

    @melvin-bot

    💬 A slack conversation has been started in #expensify-open-source

  4. carlosmiceli commented on Apr 29, 2025

    @carlosmiceli
    Contributor

    @lanitochka17 is this happening every time after failing to export the report, like it shows in the video? Or could you share a video where this bug is occurring without the failed export previously?

  5. nkdengineer commented on Apr 29, 2025

    @nkdengineer
    Contributor

    @carlosmiceli I think it's not related, my PR doesn't change anything on the report page. Maybe related to simplified PR.

  6. carlosmiceli commented on Apr 29, 2025

    @carlosmiceli
    Contributor

    @nkdengineer Yeah, tried to delete the comment because I noticed that PR right after. My bad.

    @luacmartins @aldo-expensify I think it's related to this (big) PR: #59999 - Any suggestions on what to do about this one?

  7. nkdengineer commented on Apr 29, 2025

    @nkdengineer
    Contributor

    No problem

  8. luacmartins commented on Apr 29, 2025

    @luacmartins
    Contributor

    This view is behind a beta. We can demote it and address as a follow up

  9. added and removed
    DeployBlockerCashThis issue or pull request should block deployment
    on Apr 29, 2025
  10. 30 remaining items

  11. changed the title [-]Report - No Export to [Accounting system] primary option on paid report[/-] [+][Due for payment 2025-05-20] Report - No Export to [Accounting system] primary option on paid report[/+] on May 13, 2025
  12. melvin-bot commented on May 13, 2025

    @melvin-bot

    Reviewing label has been removed, please complete the "BugZero Checklist".

  13. melvin-bot commented on May 13, 2025

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.44-8 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

    If no regressions arise, payment will be issued on 2025-05-20. 🎊

    For reference, here are some details about the assignees on this issue:

    • @suneox requires payment (Needs manual offer from BZ)
  14. melvin-bot commented on May 13, 2025

    @melvin-bot

    @suneox @strepanier03 @suneox The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]

  15. melvin-bot commented on May 20, 2025

    @melvin-bot

    Payment Summary

    Upwork Job

    • ROLE: @suneox paid $(AMOUNT) via Upwork (LINK)

    BugZero Checklist (@strepanier03)

    • 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 paid out the Upwork contracts or cancelled the ones that are incorrect
    • I have verified the payment summary above is correct
  16. suneox commented on May 20, 2025

    @suneox
    Contributor

    BugZero Checklist:

    • [Contributor] Classify the bug:
    Bug classification

    Source of bug:

    • 1a. Result of the original design (eg. a case wasn't considered)
    • 1b. Mistake during implementation
    • 1c. Backend bug
    • 1z. Other:

    Where bug was reported:

    • 2a. Reported on production (eg. bug slipped through the normal regression and PR testing process on staging)
    • 2b. Reported on staging (eg. found during regression or PR testing)
    • 2d. Reported on a PR
    • 2z. Other:

    Who reported the bug:

    • 3a. Expensify user
    • 3b. Expensify employee
    • 3c. Contributor
    • 3d. QA
    • 3z. Other:
    • [Contributor] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.

      N/A: This issue come from PR Simplified Actions on Report Header and Preview V2 #59999, which involved extensive changes across various parts of the system. Due to the complexity and number of flows described in the documentation, some cases mentioned in the description were unintentionally overlooked

    • [Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner.

      Link to discussion: [PAID] Report - No Export to [Accounting system] primary option on paid report #61092 (comment)

    • [Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.

      N/A: It isn't easy to test for this bug

  17. strepanier03 commented on May 20, 2025

    @strepanier03
    Contributor

    Payment summary

  18. changed the title [-][Due for payment 2025-05-20] Report - No Export to [Accounting system] primary option on paid report[/-] [+][PAID] Report - No Export to [Accounting system] primary option on paid report[/+] on May 20, 2025
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 productionBugSomething is broken. Auto assigns a BugZero manager.DailyKSv2Engineering

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions