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 2024-01-28] [ECARD SETTINGS] Expiration date in card details is using the wrong format #34629

Closed
kevinksullivan opened this issue Jan 17, 2024 · 19 comments
Assignees
Labels
Awaiting Payment Auto-added when associated PR is deployed to production Bug Something is broken. Auto assigns a BugZero manager. Internal Requires API changes or must be handled by Expensify staff Weekly KSv2

Comments

@kevinksullivan
Copy link
Contributor

kevinksullivan commented Jan 17, 2024

If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!


Issue reported by: @kevinksullivan
Slack conversation: https://expensify.slack.com/archives/C05DWUDHVK7/p1705442308576449

Action Performed:

  1. Set >$0 limit on card
  2. Navigate to settings > wallet > virtual card > view details

Expected Result:

The expiration date should be in the format MM/YYYY

Actual Result:

The expiration date format is in MMYY

image

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~01ff444ac3f126e525
  • Upwork Job ID: 1747738873658785792
  • Last Price Increase: 2024-01-17
@kevinksullivan kevinksullivan added Daily KSv2 Bug Something is broken. Auto assigns a BugZero manager. labels Jan 17, 2024
Copy link

melvin-bot bot commented Jan 17, 2024

Triggered auto assignment to @abekkala (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

@kevinksullivan kevinksullivan moved this to Release 4: Card Experience in [#whatsnext] Wave 05 - Deprecate Free Jan 17, 2024
@ghost
Copy link

ghost commented Jan 17, 2024

Proposal

Please re-state the problem that we are trying to solve in this issue.

[ECARD SETTINGS] Expiration date in card details is using the wrong format

What is the root cause of that problem?

The Expiration Date in

        expiration: 'Expiration date',
        expirationDate: 'MMYY',

What changes do you think we should make in order to solve the problem?

We can just add a / and also will update the format to MM/YYYY symbol to make the expiration date as needed.

What alternative solutions did you explore? (Optional)

I don't there is any alternative approach.

@ghost
Copy link

ghost commented Jan 17, 2024

Proposal Updated

aashiqc added a commit to aashiqc/App that referenced this issue Jan 17, 2024
@ghost
Copy link

ghost commented Jan 17, 2024

So is my proposal not valid? @abekkala @grgia

@abekkala
Copy link
Contributor

@kevinksullivan @grgia does this need the external label?

@grgia
Copy link
Contributor

grgia commented Jan 17, 2024

@abekkala not yet, I am triaging all the card bugs today/tomorrow first

@ghost
Copy link

ghost commented Jan 17, 2024

so my proposal is invalid or of no use @grgia

@grgia grgia added the Internal Requires API changes or must be handled by Expensify staff label Jan 17, 2024
Copy link

melvin-bot bot commented Jan 17, 2024

Job added to Upwork: https://www.upwork.com/jobs/~01ff444ac3f126e525

Copy link

melvin-bot bot commented Jan 17, 2024

Triggered auto assignment to Contributor Plus for review of internal employee PR - @mananjadhav (Internal)

@grgia
Copy link
Contributor

grgia commented Jan 17, 2024

@AnshuAgarwal24 thank you for your proposal. I am taking this internally as there are a few issues on this page with style/formatting that I decided to group together.

For next time, it's helpful to look for issues labeled with Help Wanted as those are actively reviewing proposals. It is also helpful if you post where in the code base you plan on making these changes, as your proposal on this PR repeated the expected result section, but did not go into depth on how you would make those changes.

Thanks again, let me know if you have any questions or need help finding an issue to work on!

@melvin-bot melvin-bot bot added Reviewing Has a PR in review Weekly KSv2 Awaiting Payment Auto-added when associated PR is deployed to production and removed Daily KSv2 Weekly KSv2 labels Jan 17, 2024
@melvin-bot melvin-bot bot changed the title [ECARD SETTINGS] Expiration date in card details is using the wrong format [HOLD for payment 2024-01-28] [ECARD SETTINGS] Expiration date in card details is using the wrong format Jan 21, 2024
@melvin-bot melvin-bot bot removed the Reviewing Has a PR in review label Jan 21, 2024
Copy link

melvin-bot bot commented Jan 21, 2024

Reviewing label has been removed, please complete the "BugZero Checklist".

Copy link

melvin-bot bot commented Jan 21, 2024

The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.28-0 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-01-28. 🎊

For reference, here are some details about the assignees on this issue:

  • @mananjadhav requires payment through NewDot Manual Requests

Copy link

melvin-bot bot commented Jan 21, 2024

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:

  • [@mananjadhav] The PR that introduced the bug has been identified. Link to the PR:
  • [@mananjadhav] 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:
  • [@mananjadhav] 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:
  • [@mananjadhav] Determine if we should create a regression test for this bug.
  • [@mananjadhav] 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.
  • [@abekkala] Link the GH issue for creating/updating the regression test once above steps have been agreed upon:

@mananjadhav
Copy link
Collaborator

@abekkala This is ready for payout. Can you please post a payout summary?

We don't have any offending PR for this one, and this was linked with two issues on design changes. I don't think we need regression steps for this one. @grgia wdyt?

@abekkala
Copy link
Contributor

abekkala commented Jan 29, 2024

PAYMENT DUE:

@JmillsExpensify
Copy link

$500 payment approved for @mananjadhav based on summary above.

@abekkala
Copy link
Contributor

abekkala commented Feb 1, 2024

@mananjadhav before I close this out can you confirm that you've requested payment in NewDot?

@mananjadhav
Copy link
Collaborator

@abekkala Yes I've requested and it is approved.

@mananjadhav
Copy link
Collaborator

@abekkala I think we can close this one out

@abekkala abekkala closed this as completed Feb 6, 2024
@github-project-automation github-project-automation bot moved this from Release 4: Migrate All to Collect to Done in [#whatsnext] Wave 05 - Deprecate Free Feb 6, 2024
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 Bug Something is broken. Auto assigns a BugZero manager. Internal Requires API changes or must be handled by Expensify staff Weekly KSv2
Projects
No open projects
Development

No branches or pull requests

5 participants