Closed kbecciv closed 1 year ago
Triggered auto assignment to @sonialiap (Bug
), see https://stackoverflow.com/c/expensify/questions/14418 for more details.
Platforms
in OP are β
)The money request header checkmark and the IOU details checkmark have inconsistent margins.
The marginLeft
of iouPreviewBoxCheckmark is set to 4, and moneyRequestHeaderCheckmark is set to 5.
We can modify these to be the same value, 8 as requested.
To remove the checkmark from paid IOU threads we can remove the checkmark in ReportPreview.
Reproducible
Job added to Upwork: https://www.upwork.com/jobs/~01628393c0c27440ce
Current assignee @sonialiap is eligible for the External assigner, not assigning anyone new.
Triggered auto assignment to Contributor-plus team member for initial proposal review - @mollfpr (External
)
Triggered auto assignment to @grgia (External
), see https://stackoverflow.com/c/expensify/questions/7972 for more details.
No consistency in margin left for green tick besides amount
As stated in Issue. both are using different margin
we should remove styles.moneyRequestHeaderCheckmark
and use styles.iouPreviewBoxCheckmark
as its introduced 2 years back. it will help in maintaining code for same thing.
both have same proprties except difference of 1px
.
We should update MoneyRequestHeader.js
and TaskHeader.js
to use styles.iouPreviewBoxCheckmark
instead of styles.moneyRequestHeaderCheckmark
.
None
Inconsistency between checkmark icon margin with the label
For IOUPreview
we have left margin of 4px in the message whereas for the MoneyRequestHeader
the margin of 8px(styles.ml2
) set within this latest PR.
1) We need to update the style to styles.ml1
in the MoneyRequestHeader
MenuItem
.
2) Also need to update marginLeft to 4px for class moneyRequestHeaderCheckmark
.
https://github.com/Expensify/App/blob/132358f1e844583cbeb0e5358e54d039f7f47ac0/src/components/MoneyRequestHeader.js#L145
https://github.com/Expensify/App/blob/132358f1e844583cbeb0e5358e54d039f7f47ac0/src/styles/styles.js#L3314-L3315
We need to clarify the expected result before selecting the proposal.
Money Request Report | Money Request Detail Header | Money Request Action |
---|---|---|
@shawnborton Would you help to determine what margin should be set between the amount and checkmark icon from the above places? Thanks!
Just to clarify with @trjExpensify and @JmillsExpensify - this screenshot here shouldn't exist right? I thought we fixed this elsewhere:
Then for the other screens, I think 8px makes sense but we're going to end up redoing the middle screenshot anyways, so I'm not really sure what we should do here.
Whatcha' mean by shouldn't exist? Right now the ReportPreview in the workspace chat looks like that. We haven't made it a "card" style with all those changes just yet, scan receipt is where those are.
The report action mockup I shared shouldn't have a green checkmark. The report preview card, yes. But the report action line, no.
Yeah, the report action line in the iou/expenseReport view shouldn't have a checkmark. The report preview (which right now is just in a message style) in the chat did, but given that we're killing it, may as well get rid of it now if you want. π
@shawnborton @trjExpensify We can change the margin for the first screenshot and remove the checkmark from the report action. Do you think this sounds good to you?
That works for me.
@mollfpr do any of these proposals work with the above suggestion? Thank you!
π£ It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? πΈ
@grgia Not specifically, but closest and first is @Ollyws proposal. We can set the value to 8px and removed the checkmark from the report action.
That works for me.
Same!
@mollfpr Does the Money Request Action still have the checkmark in the lastest main for you? Mine doesn't:
Edit: Actually it appears when there's a thread:
This can be removed from ReportPreview.
@grgia let's go with @Ollyws proposal which it does what requested before.
π π π C+ reviewed!
@sonialiap @mollfpr @grgia 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!
π£ @Ollyws You have been assigned to this job by @grgia! Please apply to this job in Upwork and leave a comment on the Github issue letting us know when we can expect a PR to be ready for review π§βπ» Keep in mind: Code of Conduct | Contributing π
Thanks for your patience, good to go @Ollyws!
Based on my calculations, the pull request did not get merged within 3 working days of assignment. Please, check out my computations here:
On to the next one π
Not sure about Melvin's calculations here...it took 4 days, 36 minutes and 4 seconds. Minus the weekend is 2 days and 36 minutes.
Thanks for the correction, Olly! Melvin's bad math issue was brought up internally yesterday, I'm not sure if we've created an issue to fix this yet but we're aware and I expect we will fix it ποΈ (Seems to do something with how the API is reading the Z in the timezone)
Reviewing
label has been removed, please complete the "BugZero Checklist".
The solution for this issue has been :rocket: deployed to production :rocket: in version 1.3.30-5 and is now subject to a 7-day regression period :calendar:. Here is the list of pull requests that resolve this issue:
If no regressions arise, payment will be issued on 2023-06-29. :confetti_ball:
After the hold period is over and BZ checklist items are completed, please complete any of the applicable payments for this issue, and check them off once done.
As a reminder, here are the bonuses/penalties that should be applied for any External issue:
BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:
[@mollfpr] The PR that introduced the bug has been identified. Link to the PR: [@mollfpr] 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:
No offending PR, another improvement on the IOU/money request design.
[@mollfpr] 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:
Since this is improvement on the visual, the regression step should be enough.
[@mollfpr] Determine if we should create a regression test for this bug. [@mollfpr] 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 step:
@dhanashree-sawant offer sent for reporting bug @Ollyws offer sent for fix (+bonus) @mollfpr offer sent for review (+bonus)
June 16 1:10pm (Friday) June 20 11:43am (Tuesday)
@sonialiap Accepted, thanks!
@sonialiap Accepted, Thank you!
Everyone has been paid β
If you havenβt already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Action Performed:
Expected Result:
App should maintain consistent margin between amount and green tick throughout all the reports in the flow
Actual Result:
App maintains different margin for all the green tick instances throughout all the reports in the flow
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Version Number: 1.3.22.0
Reproducible in staging?: Yes
Reproducible in production?: n/a
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
Notes/Photos/Videos: Any additional supporting documentation
https://github.com/Expensify/App/assets/93399543/6bcb7d53-e8f2-440c-a680-4510ad425f68
https://github.com/Expensify/App/assets/93399543/00fd7b75-e068-4c55-b11a-d42c5c8feb4b
Expensify/Expensify Issue URL:
Issue reported by: @dhanashree-sawant
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1685201350349499
View all open jobs on GitHub
Upwork Automation - Do Not Edit