-
Notifications
You must be signed in to change notification settings - Fork 2.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[$250] Next steps are incorrect when there is no approval on a report #42834
Comments
Triggered auto assignment to @MitchExpensify ( |
Job added to Upwork: https://www.upwork.com/jobs/~017287c932cce9e705 |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @alitoshmatov ( |
What do you think the header should say @kevinksullivan ? Something like this?; "Waiting for approval." |
@MitchExpensify, @alitoshmatov Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸 |
@MitchExpensify, @alitoshmatov 6 days overdue. This is scarier than being forced to listen to Vogon poetry! |
Going to make a call and suggest we remove next steps entirely in this situation so I've updated the OP accordingly. Waiting on proposals at this point 👀 |
What wave collect status do you think this one fits under @trjExpensify ? |
Hm, is this part of the pending/scanning implementation? @kevinksullivan didn't we talk about this one using the "finished" terminology for the closed non-reimbursable reports? |
@MitchExpensify, @alitoshmatov Now this issue is 8 days overdue. Are you sure this should be a Daily? Feel free to change it! |
@MitchExpensify @alitoshmatov this issue was created 2 weeks ago. Are we close to approving a proposal? If not, what's blocking us from getting this issue assigned? Don't hesitate to create a thread in #expensify-open-source to align faster in real time. Thanks! |
Updated the expected behavior based on the slack conversation We need proposals now |
@MitchExpensify, @alitoshmatov 10 days overdue. I'm getting more depressed than Marvin. |
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸 |
I feel like this might be hot pick worthy, what d'you reckon @trjExpensify ? |
I think we are not going to have any proposals since it requires expensify card |
@pasyukevich it looks like this might be specific to ECard transactions, which need to be QAd internally. @kevinksullivan @anmurali could you confirm |
@anmurali, @pasyukevich, @grgia, @alitoshmatov Whoops! This issue is 2 days overdue. Let's get this updated quick! |
Awaiting confirmation on expected result here |
@anmurali, @pasyukevich, @grgia, @alitoshmatov Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
solution Header: "Finished!" |
Chatted here There's three cases to fix: if single expense report and all expenses are pending or scanning show the pending/scanning banner |
I think this case
Needs to be covered in NextStep.php |
https://expensify.slack.com/archives/C03TQ48KC/p1724276550180769 |
If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results. If a regression has occurred and you are the assigned CM follow the instructions here. If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future. |
This issue has not been updated in over 15 days. @anmurali, @pasyukevich, @grgia, @alitoshmatov eroding to Monthly issue. P.S. Is everyone reading this sure this is really a near-term priority? Be brave: if you disagree, go ahead and close it out. If someone disagrees, they'll reopen it, and if they don't: one less thing to do! |
@grgia Is there anything that I can help with? |
@grgia bump here |
This seems to be done? |
@muttmuure yep this should be done |
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: 1.4.77-3
Reproducible in staging?: y
Reproducible in production?: y
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: @kevinksullivan
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1717026958410769
Action Performed:
Expected Result:
The next steps read should show:
Header: "Finished!"
Subheader: "No further action required!"
Actual Result:
Next steps say this report needs approval.
Workaround:
unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
View all open jobs on GitHub
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: