Held on the backend changes that enables the new system message.
Main issue: #56386
Doc section: Here
Project: #migrate
Feature Description
When an approver only approves the unheld transactions on a report, and the held transactions are moved to a new report, the following happens:
- a new report is optimistically created (this works already)
- We set the same creation timestamp to the new report as well as to its
CREATED reportAction, as that of the original report. This is the current issue at hand
- we optimistically copy all workflow-related actions from the original report to the new report (issue here)
- we optimistically create the system message that explains to the user that the report was created for moving the unapproved expenses from the original report (issue here)
The backend has the following logic:
- Computes the original report creation timestamps
- if the report has a
CREATED reportAction, it takes its created timestamp
- else is takes the original report
created timestamp
- Sets the timestamp computed above as the
created value for the new report
created value for the CREATED reportAction added to the new report
Let's optimistically do the same on the front-end.
Upwork Automation - Do Not Edit
- Upwork Job URL: https://www.upwork.com/jobs/~022001700507502950640
- Upwork Job ID: 2001700507502950640
- Last Price Increase: 2025-12-18
Issue Owner
Current Issue Owner: @dylanexpensify
Held on the backend changes that enables the new system message.
Part of the Hold for Advanced Approval project
Main issue: #56386
Doc section: Here
Project: #migrate
Feature Description
When an approver only approves the unheld transactions on a report, and the held transactions are moved to a new report, the following happens:
CREATEDreportAction, as that of the original report. This is the current issue at handThe backend has the following logic:
CREATEDreportAction, it takes itscreatedtimestampcreatedtimestampcreatedvalue for the new reportcreatedvalue for theCREATEDreportAction added to the new reportLet's optimistically do the same on the front-end.
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @dylanexpensify