You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Due for payment 2025-04-28] [Due for payment 2025-04-17] [Manager McTest] Tooltip Centered Incorrectly #58657
⚠️ 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 ⚠️
FYI I'm on sick leave, so I'm out of office today, I will most likely be back on Thursday, but it's possible I will come back sooner, I will keep you posted.
1a. Result of the original design (eg. a case wasn't considered)
1b. Mistake during implementation
1c. Backend bug
1z. Other:
Where bug was reported:
2a. Reported on production (eg. bug slipped through the normal regression and PR testing process on staging)
2b. Reported on staging (eg. found during regression or PR testing)
2d. Reported on a PR
2z. Other:
Who reported the bug:
3a. Expensify user
3b. Expensify employee
3c. Contributor
3d. QA
3z. Other:
[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: No need, the author already fixed it
[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:
[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.
[BugZero Assignee] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.30-4 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
BugZero Checklist: The PR adding this new feature has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:
[@DylanDylann] Please propose regression test steps to ensure the new feature will work correctly on production in further releases.
[@OfstadC] Link the GH issue for creating/updating the regression test once above steps have been agreed upon.
Activity
melvin-bot commentedon Mar 18, 2025
Triggered auto assignment to @OfstadC (
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.melvin-bot commentedon Mar 18, 2025
melvin-bot commentedon Mar 18, 2025
Triggered auto assignment to Design team member for new feature review - @shawnborton (
NewFeature)shawnborton commentedon Mar 18, 2025
Does this happen all the time or just when you resize?
JKobrynski commentedon Mar 20, 2025
Hi, I'm Julian from Callstack - expert agency - and I'd like to work on this issue!
JKobrynski commentedon Mar 24, 2025
Update:
FYI I'm on sick leave, so I'm out of office today, I will most likely be back on Thursday, but it's possible I will come back sooner, I will keep you posted.
30 remaining items
melvin-bot commentedon Apr 17, 2025
Payment Summary
Upwork Job
BugZero Checklist (@OfstadC)
OfstadC commentedon Apr 17, 2025
@DylanDylann please complete the BZ checklist so we can issue payment here. Thanks 😃
DylanDylann commentedon Apr 17, 2025
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: No need, the author already fixed it
[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:
[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.
[BugZero Assignee] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.
Link to issue: https://github.com/Expensify/Expensify/issues/491952
Regression Test Proposal
Test:
Do we agree 👍 or 👎
OfstadC commentedon Apr 17, 2025
Thanks!
Payment Summary is accurate
[-][Due for payment 2025-04-17] [Manager McTest] Tooltip Centered Incorrectly[/-][+][Due for payment 2025-04-28] [Due for payment 2025-04-17] [Manager McTest] Tooltip Centered Incorrectly[/+]melvin-bot commentedon Apr 21, 2025
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon Apr 21, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.30-4 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 2025-04-28. 🎊
For reference, here are some details about the assignees on this issue:
melvin-bot commentedon Apr 21, 2025
BugZero Checklist: The PR adding this new feature has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:
DylanDylann commentedon May 30, 2025
@OfstadC I was assigned to this issue before being eligible for NewDot payment. So I should be paid via Upwork.
OfstadC commentedon Jul 8, 2025
Chatting in Slack with @DylanDylann
OfstadC commentedon Jul 10, 2025
Updated Payment Summary