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
The violations are formatted incorrectly on the reports page when there are two or more descriptions #64059
Version Number: Reproducible in staging?: Needs Reproduction Reproducible in production?: Needs Reproduction 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:@davidcardoza Slack conversation (hyperlinked to channel name): #expensify_product
[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: NA
[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.
No, I think we can skip adding regression test because we have added unit tests to cover the changes.
Activity
melvin-bot commentedon Jun 12, 2025
Triggered auto assignment to @laurenreidexpensify (
Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.MelvinBot commentedon Jun 12, 2025
This has been labelled "Needs Reproduction". Follow the steps here: https://stackoverflowteams.com/c/expensify/questions/16989
mountiny commentedon Jun 12, 2025
Discussing with @joekaufmanexpensify if the copy should be updated instead in slack
joekaufmanexpensify commentedon Jun 12, 2025
Responded here 👍
mountiny commentedon Jun 12, 2025
@dukenv0307 so for the 530 case we want
Can't auto-match receipt due to a broken bank connection.And then the rter.brokenBankConnection (not 530) we want the same error logic as is the
brokenConnectionis trueCan you raise a PR for this please and let me know if anything is unclear
allgandalf commentedon Jun 12, 2025
I was able to reproduce this issue by importing the onyx state , can i be assinged as the C+ here as per this slack post:
https://expensify.slack.com/archives/C02NK2DQWUX/p1749726573522609
19 remaining items
melvin-bot commentedon Aug 8, 2025
Triggered auto assignment to @clarajones-expensify (
Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.laurenreidexpensify commentedon Aug 8, 2025
@clarajones-expensify I am OOO next week, can you please help with the payment on this when @eh2077 completes checklist thanks
clarajones-expensify commentedon Aug 8, 2025
@eh2077 - would you fill out this checklist? thank you!
eh2077 commentedon Aug 8, 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: https://github.com/Expensify/App/pull/50793/files#r2263263689
[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: NA
[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.
No, I think we can skip adding regression test because we have added unit tests to cover the changes.
eh2077 commentedon Aug 8, 2025
@clarajones-expensify Thanks for the reminder. Checklist completed, thanks
clarajones-expensify commentedon Aug 8, 2025
Payment Summary
Contributor: @dukenv0307 due $250 via NewDot
Contributor+: @eh2077 due $250 via NewDot
flaviadefaria commentedon Aug 13, 2025
$250 approved for @eh2077
quinthar commentedon Aug 13, 2025
$250 approved for @eh2077
garrettmknight commentedon Oct 24, 2025
$250 approved for @dukenv0307