Closed cristipaval closed 5 months ago
Triggered auto assignment to @garrettmknight (NewFeature
), see https://stackoverflowteams.com/c/expensify/questions/14418#:~:text=BugZero%20process%20steps%20for%20feature%20requests for more details. Please add this Feature request to a GH project, as outlined in the SO.
:warning: It looks like this issue is labelled as a New Feature but not tied to any GitHub Project. Keep in mind that all new features should be tied to GitHub Projects in order to properly track external CAP software time :warning:
Triggered auto assignment to Design team member for new feature review - @dannymcclain (NewFeature
)
Hi, I'm Viktoryia from Callstack - expert contributor group - and I would like to work on this issue.
Job added to Upwork: https://www.upwork.com/jobs/~011c3a6ec6a19ed908
Triggered auto assignment to Contributor-plus team member for initial proposal review - @akinwale (External
)
Hello,
I would like to work on this issue.
π£ @devhardikbeladiya! π£ 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:
Contributor details
Your Expensify account email: <REPLACE EMAIL HERE>
Upwork Profile Link: <REPLACE LINK HERE>
I would like to work on this issue.
Your Expensify account email: devhardikbeladiya@gmail.com Upwork Profile Link: https://www.upwork.com/freelancers/~015078816783129fe4
Just so I'm super clear on this: the Send invoice
option only shows up in Global create and already-created invoice rooms (that would've been created from the global create option), is that correct? That's what I'm gathering from the doc, I just want to fully make sure I understand the expected behavior/implementation.
@dannymcclain This issue is more about creating an invoice from the existing invoice room. So you have already send one invoice to the receiver, and you want to send another one. Doing it from Global create adds extra step of selecting receiver. By doing it right from the room this step can be skipped. What do you think?
@cristipaval I think the related section was removed from Invoicing document, do you have an idea where was it moved to?
@VickyStash ok that's what I thought this issue was for, just wanted to make sure! Thanks.
@shawnborton Which way the receiver should look if the user sends an invoice from the existing invoice room. I have two options: 1) 2)
Hmm I think it makes sense to reuse the same room avatar, so your first option. Curious what @davidcardoza and @puneetlath think though!
Updates: I've enabled send invoice functionality from the invoice room, just need to do some UI fixes. I think I'll open the PR for review tomorrow.
I like using the room avatar here as well.
The PR is opened for the review
+1 to room avatar.
Following through this slack conversation - https://expensify.slack.com/archives/CSL3XBCCR/p1715782572275539
Disabling invoicing at the workspace level will not affect existing invoices and invoice rooms; they will still be accessible. Although this wasn't explicitly stated in the workspace settings section of the payments design docu, I've added a bullet point to the HL overview of the document to clarify this. It's important to note that the invoice rooms will be impacted in that the "Send Invoice" option will no longer appear in the invoice room create button when invoicing is disabled in workspace settings of the invoice sender workspace.
^ @cristipaval Let me know if you think that should be it's own GH.
^ @cristipaval Let me know if you think that should be it's own GH.
I think we're good with this issue
@garrettmknight, @akinwale, @dannymcclain, @cristipaval, @VickyStash Whoops! This issue is 2 days overdue. Let's get this updated quick!
Note that this has gone to staging. When it deploys I'll test and update the payment if necessary.
On prod, updating to awaiting payment.
@garrettmknight bump for payment. Thanks.
Sorry @akinwale - offer is out to you in Upwork.
All paid out - can you complete the checklist?
- [x] [@akinwale] The PR that introduced the bug has been identified. Link to the PR:
- [x] [@akinwale] 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:
- [x] [@akinwale] A discussion in #expensify-bugs 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:
Not a regression. This is a new feature.
- [x] [@akinwale] Determine if we should create a regression test for this bug.
- [x] [@akinwale] If we decide to create a regression test for the bug, please propose the regression test steps to ensure the same bug will not reach production again.
Regression Test Steps
Do we agree π or π?
Part of the project
Main issue: https://github.com/Expensify/Expensify/issues/341717 Doc section: Here Project: #vip-billpay
Feature Description
Problem:
In NewDot, users are limited to sending invoices from Global Create. Without the ability to create and send invoices from within these dedicated rooms, the process can become disjointed. This setup forces users to navigate away from the conversation context to send invoices, disrupting workflow continuity.
Solution
Implement Send invoice from the invoice room in NewDot allowing users to send invoices directly from a pre-existing invoices room.
Manual Test Steps
Automated Tests
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @garrettmknight