Repository navigation
[Due for payment 2026-10-14] [Release 5] [App] Replace Delete with Archive behind the archivePolicies beta #97123
Description
Behind the archivePolicies beta:
- Replace the Delete menu item with Archive at the
WorkspaceRowThreeDotsMenuandWorkspaceOverviewPageentry points (archive icon,workspace.common.archivelabel). - Point Archive at a flow modeled on DeleteWorkspaceFlow that calls a new
archivePolicyaction invoking the ArchivePolicy command. - Keep the card confirmation copy and reuse the existing pre-checks (Invoicify block, outstanding-balance guard, bill calculation, pay-and-downgrade).
Design doc: https://docs.google.com/document/d/1M4-F4gR2GPfjlr3EoKu-8byVBwoYMPexwl6ttYZkb8U/edit
Tracking issue: https://github.com/Expensify/Expensify/issues/646296
Activity
truph01 commentedon Aug 7, 2026
@rlinoz I'm working on PR #98029, which uses
ArchivePolicyAPI.When will
ArchivePolicybe available so I can test the full archived policy flow?truph01 commentedon Aug 11, 2026
@rlinoz Could you check my comment above?
rlinoz commentedon Aug 11, 2026
Sorry for the delay, I will try to get to the archive command next week. There are some ongoing discussions about it.
truph01 commentedon Aug 17, 2026
@rlinoz Do you have any updates on it?
rlinoz commentedon Aug 19, 2026
Not yet, we sorted things out, I need to update the doc and get someone writing the backend.
rlinoz commentedon Aug 25, 2026
We started movin towards having the command btw, still will take some time though.
rlinoz commentedon Sep 15, 2026
FYI
ArchivePolicyshould get deployed today to staging23 remaining items
daledah commentedon Oct 12, 2026
BugZero Checklist:
[Contributor] The offending PR and associated issue have been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.
Link to the comment on the PR: N/A
[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:
[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.
[BugZero Assignee] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.
Link to issue: https://github.com/Expensify/Expensify/issues/692727
Regression Test Proposal
Precondition:
Test:
Do we agree 👍 or 👎
Zapier Logs
Run ID: 00040eee-818e-a894-cfef-2844e700a1d4melvin-bot commentedon Oct 13, 2026
Triggered auto assignment to @mallenexpensify (
Awaiting Payment)melvin-bot commentedon Oct 13, 2026
Payment Summary
Resolving PRs:
feat: Replace Delete with Archive behind the archivePolicies beta #98029
Reviewer: @truph01 owed $175 via NewDot
Reviewer: @daledah owed $175 via NewDot
BugZero Checklist (@mallenexpensify)
melvin-bot commentedon Oct 16, 2026
@mallenexpensify Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!
mallenexpensify commentedon Oct 16, 2026
@daledah this issue and/or PR mention a deploy blocker or a regression. Before the payment date, post one of the three options in step 20 of the C+ doc: it was a regression, it was not, or you did not review the offending PR. If you don't post, the default is to reduce payment.