[Due for payment 2025-09-26] Duplicate workspace - Avatar can be uploaded when duplicating workspace but not saved

@abekkala

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.2.1-0
Reproducible in staging?: Yes
Reproducible in production?: N/A - new feature, doesn't exist in prod
If this was caught during regression testing, add the test name, ID and link from TestRail: #69146
Email or phone of affected tester (no customers): applausetester+sdjoinsso@applause.expensifail.com
Issue reported by: Applause Internal Team
Device used: Mac 15.5 / Chrome
App Component: Workspace Settings

Action Performed:

Precondition:

Log in with Expensifail account.

Go to staging.expensify.com
Create a workspace with custom avatar.
Go back to workspace list.
Click 3-dot menu on the workspace.
Click Duplicate Workspace.
Click on the avatar and upload another avatar.
Click Next.
Click Continue.

Expected Result:

The new avatar from Step 6 will be the duplicated workspace's avatar.

Actual Result:

Despite uploading a new avatar when duplicating workspace, the duplicated workspace's avatar is not showing the new avatar. It shows the same custom avatar as the original workspace.

Workaround:

Unknown

Platforms:

Screenshots/Videos

1.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @abekkala

@abekkala

Triggered auto assignment to @abekkala (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.

@aldo-expensify

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

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

👋 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:

Identify the pull request that introduced this issue and revert it.
Find someone who can quickly fix the issue.
Fix the issue yourself.

@dejavu60johncastro

📣 @dejavu60johncastro! 📣
Hey, it seems we don’t have your contributor details yet! You'll only have to do this once, and this is how we'll hire you on Upwork.
Please follow these steps:

Make sure you've read and understood the contributing guidelines.
Get the email address used to login to your Expensify account. If you don't already have an Expensify account, create one here. If you have multiple accounts (e.g. one for testing), please use your main account email.
Get the link to your Upwork profile. It's necessary because we only pay via Upwork. You can access it by logging in, and then clicking on your name. It'll look like this. If you don't already have an account, sign up for one here.
Copy the format below and paste it in a comment on this issue. Replace the placeholder text with your actual details.

Format:

Contributor details
Your Expensify account email: <REPLACE EMAIL HERE>
Upwork Profile Link: <REPLACE LINK HERE>

@mountiny

@mountiny #69042 probably the same
And #69146 (comment) comment from C+

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

@narefyev91

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

Fix saving avatar when duplicating policy #70255

If no regressions arise, payment will be issued on 2025-09-26. 🎊

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

@narefyev91 does not require payment (Contractor)
@jnowakow does not require payment (Contractor)
@DylanDylann requires payment through NewDot Manual Requests

@DylanDylann

@DylanDylann @abekkala 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]

@jnowakow

PAYMENT SUMMARY FOR SEPT 26

Fix: @jnowakow [no payment needed]
PR Review: @DylanDylann [$250] Payment via NewDot
please complete checklist

@narefyev91

Payment Summary

Upwork Job

Contributor: @narefyev91 is from an agency-contributor and not due payment
Contributor: @jnowakow is from an agency-contributor and not due payment
Reviewer: @DylanDylann owed $250 via NewDot

BugZero Checklist (@abekkala)

(if NewFeature) I have created a PR for any necessary HelpDot updates, or I confirmed no updates are necessary.
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

@DylanDylann

@DylanDylann bumping this one. Can you complete the checklist so we can close this one out for NewDot payment?

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:

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

Link to comment: This bug is known in the implementation phase, but it is related to BE. We fix it separately here
[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/552505

Regression Test Proposal

Precondition:

Test:

Go to workspaces page.
Click three dots -> Duplicate Workspace
Select custom avatar and continue
Duplicate workspace.
Verify that the avatar selected in step 3 is saved

Do we agree 👍 or 👎

@jnowakow

posting payment summary once more for better visibility

PAYMENT SUMMARY FOR SEPT 26

Fix: @jnowakow [no payment needed]
PR Review: @DylanDylann [$250] Payment via NewDot
thank you! 🎉

@DylanDylann

approved $250 for @DylanDylann.

Navigation Menu

Repository navigation

[Due for payment 2025-09-26] Duplicate workspace - Avatar can be uploaded when duplicating workspace but not saved #69724

Action Performed:

Expected Result:

Actual Result:

Workaround:

Platforms:

Screenshots/Videos

31 remaining items

PAYMENT SUMMARY FOR SEPT 26

Payment Summary

BugZero Checklist (@abekkala)

BugZero Checklist:

Regression Test Proposal

Precondition:

Test:

PAYMENT SUMMARY FOR SEPT 26

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

[Due for payment 2025-09-26] Duplicate workspace - Avatar can be uploaded when duplicating workspace but not saved #69724

Description

Action Performed:

Expected Result:

Actual Result:

Workaround:

Platforms:

Screenshots/Videos

Activity

melvin-bot commented on Sep 3, 2025

melvin-bot commented on Sep 3, 2025

melvin-bot commented on Sep 3, 2025

github-actions commented on Sep 3, 2025

melvin-bot commented on Sep 3, 2025

narefyev91 commented on Sep 3, 2025

31 remaining items

melvin-bot commented on Sep 19, 2025

melvin-bot commented on Sep 19, 2025

melvin-bot commented on Sep 19, 2025

abekkala commented on Sep 26, 2025

PAYMENT SUMMARY FOR SEPT 26

melvin-bot commented on Sep 26, 2025

Payment Summary

BugZero Checklist (@abekkala)

abekkala commented on Sep 29, 2025

DylanDylann commented on Sep 30, 2025

BugZero Checklist:

Regression Test Proposal

Precondition:

Test:

abekkala commented on Sep 30, 2025

PAYMENT SUMMARY FOR SEPT 26

trjExpensify commented on Nov 24, 2025

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions