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

Sponsor Invoices: "State/Province" becomes "Not Applicable" on address and QB invoice if left blank #656

Open
ghost opened this issue Oct 16, 2017 · 2 comments
Labels
[Component] Payments Payment tools, budgets, invoices [Component] Quickbooks Migrated from Trac [Type] Good First Issue Straightforward, self-contained, doesn't require deep knowledge of codebase

Comments

@ghost
Copy link

ghost commented Oct 16, 2017

Imported from https://meta.trac.wordpress.org/ticket/3203
Created by @Varantain:

If the sponsor's "State / Province" field is left blank, it appears as "Not Applicable" on the sponsor's address when an invoice is submitted to be issued, and also on the actual invoice generated by QuickBooks.

@ghost
Copy link
Author

ghost commented Oct 16, 2017

Comment by @coreymckrill:

  • Keywords set to Needs Patch Good First Bug

I believe this is intentional because some countries don't have states/provinces or use them in their address schemas.

Seems like "Not Applicable" shouldn't appear on the actual generated invoice, though.

@ghost
Copy link
Author

ghost commented Apr 2, 2020

Comment by slackbot:

This ticket was mentioned in Slack in #meta-wordcamp by iandunn. View the logs.

@ghost ghost added Migrated from Trac [Type] Good First Issue Straightforward, self-contained, doesn't require deep knowledge of codebase labels Sep 24, 2020
@ryelle ryelle added [Component] Quickbooks [Component] Payments Payment tools, budgets, invoices labels Sep 30, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Component] Payments Payment tools, budgets, invoices [Component] Quickbooks Migrated from Trac [Type] Good First Issue Straightforward, self-contained, doesn't require deep knowledge of codebase
Projects
None yet
Development

No branches or pull requests

1 participant