Repository navigation
[HOLD for payment 2024-11-29] Not able to submit expense to Expenses - Expensify CA workspace #52515
Description
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:
Reproducible in staging?: needs reproduction
Reproducible in production?: needs reproduction
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?:
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: @justinpersaud
Slack conversation (hyperlinked to channel name): expensify_migrate
Action Performed:
- Go to Expenses - Expensify CA workspace.
- Click on + sign
- Click global create
- Submit expense
- Enter amount
- Select the workspace Expenses - Expensify CA workspace
- Submit the expense
Expected Result:
- in step 2 "submit expense" should be available
- Expense should be available in the workspace after created
Actual Result:
- in step 2 "submit expense" is not available
- Expense disappears in the workspace after created
Workaround:
unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
- Android: Standalone
- Android: HybridApp
- Android: mWeb Chrome
- iOS: Standalone
- iOS: HybridApp
- iOS: mWeb Safari
- MacOS: Chrome / Safari
- MacOS: Desktop
Screenshots/Videos
Add any screenshot/video evidence
Issue Owner
Current Issue Owner: @kadiealexanderMetadata
Metadata
Assignees
Labels
Type
Projects
- Status
Activity
melvin-bot commentedon Nov 14, 2024
Triggered auto assignment to @kadiealexander (
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.MelvinBot commentedon Nov 14, 2024
This has been labelled "Needs Reproduction". Follow the steps here: https://stackoverflowteams.com/c/expensify/questions/16989
kadiealexander commentedon Nov 14, 2024
I'm not able to reproduce this (I'm not in the CA workspace and I can't repro with the AU workspace) - @aldo-expensify or @luacmartins would either of you be able to try reproduce this for us?
luacmartins commentedon Nov 14, 2024
Yea, I don't have the submit option from within the workspace chat.
kadiealexander commentedon Nov 18, 2024
Not overdue!
9 remaining items
mountiny commentedon Nov 19, 2024
PR up
[-]Not able to submit expense to `Expenses - Expensify CA` workspace[/-][+][HOLD for payment 2024-11-29] Not able to submit expense to `Expenses - Expensify CA` workspace[/+]melvin-bot commentedon Nov 22, 2024
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon Nov 22, 2024
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.65-5 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 2024-11-29. 🎊
melvin-bot commentedon Nov 22, 2024
@mountiny @kadiealexander @mountiny 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]
heyjennahay commentedon Nov 27, 2024
Confirming this issue has been resolved for me
mountiny commentedon Nov 28, 2024
BugZero Checklist:
Bug classification
Source of bug:
Where bug was reported:
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 is a migration issue and new expensify account was not whilabelled as participant
[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: This already started in Slack
[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.
Regression Test Proposal Template
[BugZero Assignee] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.
Link to issue: No need
Regression Test Proposal
Precondition:
Test:
Do we agree 👍 or 👎