[HOLD for payment 2024-12-03] [HOLD FOR #52893] [Company Cards] Card number is not visible in the cards table #52915
Description
Coming from here
When connecting a direct feed connection, we are missing the last 4 pan number in the company cards feed table.
Issue Owner
Current Issue Owner: @isabelastisserReacted by Gandalf
Metadata
Metadata
Assignees
Labels
Type
Projects
- Status
Activity
melvin-bot commentedon Nov 21, 2024
Triggered auto assignment to @isabelastisser (
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.VickyStash commentedon Nov 21, 2024
Hi, I'm Viktoryia from Callstack - expert contributor group - and I would like to work on this issue.
VickyStash commentedon Nov 21, 2024
The issue will be fixed in this PR: #52893 (comment)
6 remaining items
[-][HOLD FOR #52893] [Company Cards] Card number is not visible in the cards table [/-][+][HOLD for payment 2024-12-03] [HOLD FOR #52893] [Company Cards] Card number is not visible in the cards table [/+]melvin-bot commentedon Nov 26, 2024
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon Nov 26, 2024
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.66-8 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 2024-12-03. 🎊
For reference, here are some details about the assignees on this issue:
melvin-bot commentedon Nov 26, 2024
@mountiny @isabelastisser @VickyStash The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]
melvin-bot commentedon Dec 3, 2024
Skipping the payment summary for this issue since all the assignees are employees or vendors. If this is incorrect, please manually add the payment summary SO.
mountiny commentedon Dec 3, 2024
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: the author of the PR addressed this issue
[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.
Regression Test Proposal Template
[BugZero Assignee] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.
Link to issue: No need for regression test
Regression Test Proposal
Precondition:
Test:
Do we agree 👍 or 👎
mountiny commentedon Dec 3, 2024
Noone to pay here now and no need for regression testing