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 2022-01-27] Update copy used in ValidationStep when bank account is verifying #6980

Closed
rosegrech opened this issue Jan 3, 2022 · 29 comments
Assignees
Labels
AutoAssignerTriage Auto assign issues for triage to an available triage team member Awaiting Payment Auto-added when associated PR is deployed to production External Added to denote the issue can be worked on by a contributor Help Wanted Apply this label when an issue is open to proposals by contributors Weekly KSv2

Comments

@rosegrech
Copy link

Problem

From this GH, noticed some punctuation items that should be corrected. See the solution for the deets.

Solution

In this screenshot, there seem to be some small punctuation issues to address:

image

  • We use "!" 3x times which we try to avoid in such short copy.
  • "No, let's start over" has no punctuation where the previous action has "!". We should be consistent in punctuation use not only in the same view/screen but throughout the platform. I have no clue if we use punctuations for such areas. If so, let's use "." vs "!".
  • Suggested copy tweak as the "but" was not sounding great to my ears :)

Thanks for doing that! Now, we just need your help verifying some info, which we can work out quickly over chat. Ready?

In this screenshot, we should have periods "." at the end of each sentence.

image

@rosegrech rosegrech added AutoAssignerTriage Auto assign issues for triage to an available triage team member Daily KSv2 labels Jan 3, 2022
@MelvinBot
Copy link

Triggered auto assignment to @JmillsExpensify (AutoAssignerTriage), see https://stackoverflow.com/c/expensify/questions/4749 for more details.

@MelvinBot MelvinBot removed the AutoAssignerTriage Auto assign issues for triage to an available triage team member label Jan 3, 2022
@rosegrech rosegrech added AutoAssignerTriage Auto assign issues for triage to an available triage team member External Added to denote the issue can be worked on by a contributor labels Jan 3, 2022
@MelvinBot
Copy link

Current assignee @JmillsExpensify is eligible for the AutoAssignerTriage assigner, not assigning anyone new.

@MelvinBot
Copy link

Current assignee @JmillsExpensify is eligible for the External assigner, not assigning anyone new.

@mdneyazahmad
Copy link
Contributor

mdneyazahmad commented Jan 3, 2022

Proposal

We need to make these changes.

  1. No change
    letsFinishInChat: 'Let\'s finish in chat!',

Spanish

letsFinishInChat: '¡Continuemos en el chat!',

2 Remove ! mark in the end

letsChatCTA: 'Yes, let\'s chat!',

Spanish

-letsChatCTA: '¡Sí, vamos a chatear!',
+letsChatCTA: 'Sí, vamos a chatear',
  1. No change
    noLetsStartOver: 'No, let\'s start over',

Spanish

noLetsStartOver: 'No, empecemos de nuevo',
  1. Change ! to . (period)
    letsChatText: 'Thanks for doing that! We need your help verifying a few pieces of information, but we can work this out quickly over chat. Ready?',

Spanish

-letsChatText: '¡Gracias! Necesitamos tu ayuda para verificar la información, pero podemos hacerlo rápidamente a través del chat. ¿Estás listo?',

+letsChatText: 'Gracias Necesitamos tu ayuda para verificar la información, pero podemos hacerlo rápidamente a través del chat. ¿Estás listo?',
  1. Add .(period) in the end
    description: 'A day or two after you add your account to Expensify we send three (3) transactions to your account. They have a merchant line like "Expensify, Inc. Validation"',

Spanish

-description: 'Uno o dos días después de agregar su cuenta a Expensify, enviamos tres (3) transacciones a su cuenta. Tienen una línea comercial como "Expensify, Inc. Validation"',
+description: 'Uno o dos días después de agregar su cuenta a Expensify, enviamos tres (3) transacciones a su cuenta. Tienen una línea comercial como "Expensify, Inc. Validation."',
  1. Add .(period) in the end
    descriptionCTA: 'Please enter each transaction amount in the fields below. Example: 1.51',

Spanish

-descriptionCTA: 'Please enter each transaction amount in the fields below. Example: 1.51',
+descriptionCTA: 'Please enter each transaction amount in the fields below. Example: 1.51.',

@rosegrech
Copy link
Author

Yup and additionally this copy change for the first screenshot:

Thanks for doing that! Now, we just need your help verifying some info, which we can work out quickly over chat. Ready?

@marcaaron
Copy link
Contributor

marcaaron commented Jan 4, 2022

Hey @rosegrech seems like we already have an issue for the header text here #6900

Can we change this issue title to something else to be sure the other changes you are suggesting get addressed separately? We now have two issues that are both proposing similar issues with their titles.

@rosegrech
Copy link
Author

sure thing. I have no clue what to call it though which is why I used similar text but have the beginning different

@marcaaron marcaaron changed the title Update copy: When bank account is pending a "Test transactions" Update copy used in ValidationStep when bank account is verifying Jan 4, 2022
@marcaaron
Copy link
Contributor

gotchu!

@JmillsExpensify
Copy link

Sorry for the delay! Catching on my next steps now.

@MelvinBot MelvinBot removed the Overdue label Jan 7, 2022
@JmillsExpensify
Copy link

Issue looks good with Marc's suggestion (e.g. clarifying the updates outside the header). I've also posted the job to Upwork here: https://www.upwork.com/jobs/~0128c8d14a0f1522c5.

@botify botify removed the Daily KSv2 label Jan 7, 2022
@MelvinBot MelvinBot added the Weekly KSv2 label Jan 7, 2022
@MelvinBot
Copy link

Triggered auto assignment to Contributor-plus team member for initial proposal review - @rushatgabhane (Exported)

@MelvinBot MelvinBot added the Help Wanted Apply this label when an issue is open to proposals by contributors label Jan 7, 2022
@MelvinBot
Copy link

Triggered auto assignment to @AndrewGable (Exported), see https://stackoverflow.com/c/expensify/questions/7972 for more details.

@rushatgabhane
Copy link
Member

rushatgabhane commented Jan 7, 2022

@mdneyazahmad I believe you need to make the same changes for es.js too.
Does spanish punctuation work the same way?

Otherwise the proposal is fine.

@mdneyazahmad
Copy link
Contributor

mdneyazahmad commented Jan 9, 2022

@rushatgabhane I updated the proposal to include the respective changes in es.js too. I am not confident about the changes. Maybe someone else who knows Spanish language can help us move forward.

#6980 (comment)

@rushatgabhane
Copy link
Member

letsChatText: 'Gracias Necesitamos

@mdneyazahmad pretty sure there's a period after Gracias.
Asked on slack for verifying Spanish punctuation.

@rushatgabhane
Copy link
Member

rushatgabhane commented Jan 11, 2022

🎀👀🎀 C+ reviewed
@mdneyazahmad's proposal is fine. Confirmed on slack

cc: @AndrewGable

@AndrewGable
Copy link
Contributor

Looks good 👍

@rushatgabhane
Copy link
Member

@mdneyazahmad small nudge, looks like you have a go ahead for a PR.

@rushatgabhane
Copy link
Member

@mdneyazahmad please let us know when you can submit a PR. Thank you so much 😄

@mdneyazahmad
Copy link
Contributor

@rushatgabhane My PR is ready, but I am unable to navigate to the screen and test. Could you please help me with test steps?

@rushatgabhane
Copy link
Member

rushatgabhane commented Jan 18, 2022

Good question. It's in workspace -> connect bank account manually. I tried setting it up using expensifail, but it asked for identity verification in step 4.

@mdneyazahmad what you could instead do is change the conditions in ReimbursementAccoutPage, and ValidationStep so that step 5 is rendered directly. I hope that helps.

@mdneyazahmad
Copy link
Contributor

mdneyazahmad commented Jan 18, 2022

@rushatgabhane Thank you for your help. I will submit my PR soon.

@botify botify added Weekly KSv2 Awaiting Payment Auto-added when associated PR is deployed to production and removed Weekly KSv2 labels Jan 20, 2022
@botify
Copy link

botify commented Jan 20, 2022

The solution for this issue has been 🚀 deployed to production 🚀 in version 1.1.31-1 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 2022-01-27. 🎊

@botify botify changed the title Update copy used in ValidationStep when bank account is verifying [HOLD for payment 2022-01-27] Update copy used in ValidationStep when bank account is verifying Jan 20, 2022
@JmillsExpensify
Copy link

@rushatgabhane Mind applying to to the linked Upwork job above so that we can submit payment? Thank you!

@rushatgabhane
Copy link
Member

https://www.upwork.com/jobs/~0128c8d14a0f1522c5

@JmillsExpensify I've already applied 😄

@JmillsExpensify
Copy link

Haha sorry for my confusion. Settling up now.

@JmillsExpensify
Copy link

Separately, @mdneyazahmad I meant to ask you to make sure to apply as well. 😄 Ooops. Mind applying quick so we can process everything in one go?

@mdneyazahmad
Copy link
Contributor

@JmillsExpensify applied

@JmillsExpensify
Copy link

I think we should officially be settled up on this issue. Thank you and don't hesitate to reach out if I'm missed something!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
AutoAssignerTriage Auto assign issues for triage to an available triage team member Awaiting Payment Auto-added when associated PR is deployed to production External Added to denote the issue can be worked on by a contributor Help Wanted Apply this label when an issue is open to proposals by contributors Weekly KSv2
Projects
None yet
Development

No branches or pull requests

8 participants