You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Default workflow is strikethrough after removing additional approver in another workflow #78327
Version Number: 9.2.86-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 BrowserStack:#76032 Email or phone of affected tester (no customers):applausetester+sdj0mssjsdidnsod1@applause.expensifail.com Issue reported by: Applause Internal Team Bug source: Pull Request QA execution Device used: Mac 26.1 / Chrome App Component: Workspace Settings
Action Performed:
Precondition:
Invite User B and C to the workspace.
Go to staging.new.expensify.com
Go to workspace settings > Workflows.
Click Add approval workflow.
Select User B as submitter.
Select User B as approver.
Enter limit and select User C as additional approver.
Tap Next
Tap Add workflow
Go offline.
Go to Members and remove User C.
Go back to Workflows tab.## Expected Result:efault workflow will not be strikethrough.
Actual Result:
Default workflow is strikethrough after removing additional approver in another workflow.
👋 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.
Activity
melvin-bot commentedon Dec 23, 2025
Triggered auto assignment to @brianlee-expensify (
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.melvin-bot commentedon Dec 23, 2025
You have been assigned to this deploy blocker because you recently merged this PR: #76032
melvin-bot commentedon Dec 23, 2025
💬 A slack conversation has been started in #expensify-open-source
github-actions commentedon Dec 23, 2025
👋 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:
abzokhattab commentedon Dec 23, 2025
Default workflow is strikethrough because the approver you removed was the main approvel in the default approval
i think this is the same as #78342
cc @JS00001
IuliiaHerets commentedon Dec 23, 2025
MacOS Monterey / Chrome
Web 9.2.86-1
No Limit field.
Reproduced with strikethrough
Screen.Recording.2025-12-23.at.15.52.05.mp4
aimane-chnaif commentedon Dec 23, 2025
@IuliiaHerets can you please check in production?
IuliiaHerets commentedon Dec 23, 2025
@aimane-chnaif The same result on prod 9.2.85-7
Screen.Recording.2025-12-23.at.16.38.35.mp4
aimane-chnaif commentedon Dec 23, 2025
Thanks. So this is not blocker as happening on production.
melvin-bot commentedon Dec 27, 2025
@JS00001, @brianlee-expensify Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!
JS00001 commentedon Dec 29, 2025
Looks like this was fixed by the revert, so going to close out