Skip to content
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

[HOLD for payment 2023-09-12] Design clean-up and consistency across expense reports and requests. #26138

Closed
JmillsExpensify opened this issue Aug 28, 2023 · 42 comments
Assignees
Labels
Awaiting Payment Auto-added when associated PR is deployed to production Daily KSv2 Design NewFeature Something to build that is a new item.

Comments

@JmillsExpensify
Copy link

JmillsExpensify commented Aug 28, 2023

We've been making a lot of fast-and-loose changes to requests and reports as part of waves3-wave5, and as a result of adding merchant names for wave4, the end result isn't what we intended. Accordingly, this is a summary of what's broken and needs to be fixed.

  1. We're showing right carets for all report and request previews, when instead right carets should be removed from all request and report previews.

  2. Similarly, IOU reports are showing the merchant when they should instead be showing the description (because IOUs always have the same merchant, which is Request).

Image

  1. When a merchant name exists for an expense / request preview, we only show the merchant.

Image

  1. We're missing the X requests logic on report previews in the workspace chat. More specifically, when more than one request exists on the expense report, we replace the merchantName with X requests, where X is the number of requests on the report. We also show up to three receipt images in the report preview. If more than three receipts exist, then we show an overlay in the lower right corner of the right most receipt, +X. This overlay counts the number of additional receipts (e.g. receipts over 3) that exist on the report but can't be seen. Examples for completeness.
    Image
@JmillsExpensify JmillsExpensify self-assigned this Aug 28, 2023
@JmillsExpensify JmillsExpensify added the NewFeature Something to build that is a new item. label Aug 28, 2023
@melvin-bot
Copy link

melvin-bot bot commented Aug 28, 2023

Current assignee @JmillsExpensify is eligible for the NewFeature assigner, not assigning anyone new.

@mountiny
Copy link
Contributor

@koko57 would you be up for this one?

@koko57
Copy link
Contributor

koko57 commented Aug 29, 2023

Sorry, I'll be ooo from tomorrow till 10th Sept., so maybe someone else from my team could take it?

@JmillsExpensify
Copy link
Author

@mountiny @luacmartins can we get someone else on this one given the OOO? I think we really need to have these items cleaned up ahead of 6th September for the product promotions.

@luacmartins luacmartins self-assigned this Aug 30, 2023
@luacmartins
Copy link
Contributor

asked here

@mountiny
Copy link
Contributor

Also asked if any C+ has time to tackle this https://expensify.slack.com/archives/C02NK2DQWUX/p1693362407056109 I think Callstack might have a bit less availability now ahead of RNEU conference.

@JmillsExpensify
Copy link
Author

Nice, thanks ya'll!

@rushatgabhane
Copy link
Member

rushatgabhane commented Aug 30, 2023

Hi, I can work on this if no one from callstack has bandwidth

@mountiny
Copy link
Contributor

@rushatgabhane Michael should be able to, you could do c+ role here to help with the code review

@rushatgabhane
Copy link
Member

Okay, so to be clear I'm just reviewing the PR that Michael will raise?

@rezkiy37
Copy link
Contributor

Hi, I'm Michael (Mykhailo) from Callstack and I would like to work in this issue.

@rushatgabhane
Copy link
Member

@rezkiy37 let's do this!

@rezkiy37
Copy link
Contributor

@JmillsExpensify, just to clarify the 4th step. The app already handles cases with one or multiple requests and receipts. I see only one discrepancy associated with the overlay, that counts the number of additional receipts.

const previewSubtitle = hasOnlyOneReceiptRequest
? transactionsWithReceipts[0].merchant
: props.translate('iou.requestCount', {
count: numberOfRequests,
scanningReceipts: numberOfScanningReceipts,
});

Example: multiple and more than 3 receipts 1
Example: multiple and scanning 2
Example: single 3

So, based on this investigation, I think we need to fix the overlay. Am I right? Please correct me if I am wrong 🙂

@mountiny
Copy link
Contributor

We also need to fix this for a normal Cash requests, thats where it was not working and I agree with the overlay issue here
image the cards are no visible

@rezkiy37
Copy link
Contributor

rezkiy37 commented Aug 30, 2023

@mountiny, do you mean this case:

Screen.Recording.2023-08-30.at.18.56.24.mov

Should we add a counter under the amount?

@JmillsExpensify
Copy link
Author

So, based on this investigation, I think we need to fix the overlay. Am I right? Please correct me if I am wrong 🙂

@rezkiy37 Yes you're exactly right! Thank you for confirming.

@mountiny
Copy link
Contributor

@rezkiy37 Yes correct, there should be the counter same as for the receipts or distance!

@rezkiy37
Copy link
Contributor

@JmillsExpensify, is it possible to provide access for a design for this specific component? I am not sure, that I can do it precisely without colors, dimensions and so on. Thank you!

Screenshot 2023-08-31 at 10 42 05

@mountiny
Copy link
Contributor

I am actually not sure if we want that design

@mountiny
Copy link
Contributor

ready for the payment

@melvin-bot melvin-bot bot added Overdue and removed Overdue labels Sep 14, 2023
@luacmartins
Copy link
Contributor

I think we're just waiting on payment here

@melvin-bot melvin-bot bot added Overdue and removed Overdue labels Sep 18, 2023
@luacmartins
Copy link
Contributor

@JmillsExpensify can you help with payment please?

@melvin-bot melvin-bot bot added Overdue and removed Overdue labels Sep 21, 2023
@luacmartins
Copy link
Contributor

Bump @JmillsExpensify for payment

@melvin-bot melvin-bot bot added Overdue and removed Overdue labels Sep 25, 2023
@shawnborton
Copy link
Contributor

Still waiting for payment?

@melvin-bot melvin-bot bot added Overdue and removed Overdue labels Sep 28, 2023
@shawnborton
Copy link
Contributor

Still waiting for payment

@mountiny
Copy link
Contributor

mountiny commented Oct 4, 2023

We only need to pay $500 to @situchan here, otherwise nothing to pay and we can close this.

@JmillsExpensify
Copy link
Author

Offer sent to @situchan.

@melvin-bot melvin-bot bot added the Overdue label Oct 10, 2023
@JmillsExpensify
Copy link
Author

Offer accepted and paid.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Awaiting Payment Auto-added when associated PR is deployed to production Daily KSv2 Design NewFeature Something to build that is a new item.
Projects
No open projects
Development

No branches or pull requests

10 participants