Closed Bug 1490727 Opened 7 years ago Closed 6 years ago

Implement one time, recurring payment workflow on MDN

Categories

(developer.mozilla.org Graveyard :: General, enhancement, P1)

Product:
developer.mozilla.org Graveyard
Component:
General
Platform:
All
Other
Type:
enhancement

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: atopal, Assigned: atopal)

Details

(Keywords: in-triage, Whiteboard: [specification][type:feature][points=6+])

What problem would this feature solve? ====================================== People would like to give back to MDN and ensure MDN not only continues to exist but gets better over time. We should give them an option to make a one time payment to MDN. Who has this problem? ===================== All visitors to MDN How do you know that the users identified above have this problem? ================================================================== Zurb ran a survey that indicated that 93% of MDN users would like to contribute to MDN How are the users identified above solving this problem now? ============================================================ There is no way to make one time payments to MDN today Do you have any suggestions for solving the problem? Please explain in detail. ============================================================================== Implement a one time payment workflow. Is there anything else we should know? ======================================
Group: mozilla-employee-confidential
Apologies, this should not have been filed as a security bug.
Group: websites-security
FWIW, if you would like security evaluation of the payment function, let us know and we'll get you in touch with the right folks.
Adding Caglar who reviewed Stripe for us in bug #1485008. Caglar, we'll needinfo you here once we have something to review. Let me know please, if that's not the right way to do it :)
Sure thing :atopal. Happy to help myself, or put you in contact with other security teams if needed.
We do have: https://donate.mozilla.org/ So if you'd like to contribute to MDN, this is a good place to do it. :)
That's a misconception unfortunately. While the foundation does valuable work and should be supported, none of that goes to MDN.
Keywords: in-triage
Priority: -- → P1
Whiteboard: [specification][type:feature] → [specification][type:feature][points=6+]
This launched with this schedule: Oct 1: Beta users Oct 2: Logged-in users Oct 3 (Today): Logged-in users, 1% of anonymous users (dwf_contrib_beta cookie) The banner goes away for 5 days if closed, or after a contribution, based on a value stored in local storage. The always-on page is https://developer.mozilla.org/en-US/contribute. Blog post by Ali Spivak and Kadir Topal: https://hacks.mozilla.org/2018/10/a-new-way-to-support-mdn/ Localization is planned for the future, after gathering data. Related pull requests so far (bugbot can't annotate confidential bugs) https://github.com/mozilla/kuma/pull/4970 - WIP: MDN Contribution payment flow implementation https://github.com/mozilla/kuma/pull/4974 - Add stripe dependency https://github.com/mozilla/kuma/pull/4975 - Contribution views prototype https://github.com/mozilla/kuma/pull/4976 - Contribution views flow https://github.com/mozilla/kuma/pull/4977 - Updates for user testing branch https://github.com/mozilla/kuma/pull/4995 - Fix contrib_beta waffle chec https://github.com/mozilla/kuma/pull/4995 - Payment flow implementation, Bugfixes, Review fixes, Code tidy https://github.com/mozilla/kuma/pull/5004 - defer stripejsand load async https://github.com/mozilla/kuma/pull/5005 - Various blockers for release. https://github.com/mozilla/kuma/pull/5006 - Exclude CSRF checking from Stripe contribute webhook https://github.com/mozilla/kuma/pull/5008 - Update copy https://github.com/mozilla/kuma/pull/5009 - More copy updates for contributions https://github.com/mozilla/kuma/pull/5011 - tweak thank-you copy for contributions https://github.com/mozilla/kuma/pull/5012 - update thank-you html email copy https://github.com/mozilla/kuma/pull/5013 - Use correct static URL in thank you email. https://github.com/mozilla/kuma/pull/5014 - More contributions updates https://github.com/mozilla/kuma/pull/5017 - Update copy and minor bugs. https://github.com/mozilla/kuma/pull/5020 - fix typo in answer to FAQ #1 https://github.com/mozilla/kuma/pull/5021 - Analytic structure update and code cleanup.
Assignee: nobody → a.topal
Group: mozilla-employee-confidential
Status: NEW → ASSIGNED
Commit pushed to master at https://github.com/mozilla/kuma https://github.com/mozilla/kuma/commit/51f9ec108dbd8732f739b6a3fc45877edf00443c bug 1490727: Rename /contribute to /payments (#5039) * Implements feedback from MDN team * Fix issue with static files in thank you email * Update analytics with semantic naming convention * Addressed PR feedback, fixed analytic events. * Fix multi-line comments * cleanup and remove blankline * Multiply submission analytic values. * Added value to `completed` analytics event. * rename static file paths * Rename backend views and urls to `payments` * fixed tests, redirect issue for contribution and some small issues * Update JS bundle name.
We're moving on to the next phase of the project, allowing a user to sign-up for monthly recurring payments. The minimal implementation is scheduled for November 15th, with the Potato team doing the majority of the work. Rather than collect that work in a new bug, I'm adjusting the focus of this bug.
Summary: Implement one time payment workflow on MDN → Implement one time, recurring payment workflow on MDN
Commit pushed to master at https://github.com/mozilla/kuma https://github.com/mozilla/kuma/commit/ae7e283bf8fd1ce4863c836f2faf5f80c4c784ae bug 1490727: Fix payment submission analytic event and add error event. (#5048) * Redirect user in analytic callback to ensure it is fired Add a timeout for analytic callback Add new event for thank-you page Add new error for contribute/error * Using session storage to trigger analytics on confirmation pages. * Move file to new name convention. * Rename static path to keep convention * Addressing PR feedback by commenting and cleaning code. * Added data as to where the submission happend * Address PR feedback, seperate confirmation page logic * Update event labels, added amount and label on payment error event. * Update event category name
Commits pushed to master at https://github.com/mozilla/kuma https://github.com/mozilla/kuma/commit/00fcf077c5558f8f3dded7e7ac4c06337fae96bc bug 1490727: Clairify tax status of Foundation Update payments FAQ #5 to clarify that Foundation donations are tax-deductible in the US, and not generally in other places. Link to the FAQ entry for more details. https://github.com/mozilla/kuma/commit/a54eb88a776dff1d2c4343b115ecc194b1947b5b Merge pull request #5050 from jwhitlock/payments-tax-faq-1490727 bug 1490727: Clairify tax status of Foundation
Commits pushed to master at https://github.com/mozilla/kuma https://github.com/mozilla/kuma/commit/4e64e88325b4ac6e04dc614610bebf24d58f7ebd bug 1490727: Add {% translation %} tag Add a Jinja2 extension that provides a {% translation %} tag that allows overriding the translation for a block of markup. This will be used to force English until we're ready to ship translations. https://github.com/mozilla/kuma/commit/7fd2f12996e09d4124b9b1afefe434e7db447984 bug 1490727: Force English for payments form Force English for the payments form, when it appears as a banner or as part of the permanent page. Also force the thank-you text to English. Allow the FAQ and the support form to be translated. This allows Pontoon contributors to prepare translations, so that they will be ready when we ship non-English locales. https://github.com/mozilla/kuma/commit/3ffe1e4f70d180fbea0bcb591adf5c32508bae77 bug 1490727: Use locale links in payments Use the user's locale in links instead of forcing English. Link text remains in English. https://github.com/mozilla/kuma/commit/f9bb5ef26f2109deeced05dd5b9a5e887ad1b0e1 Merge pull request #5052 from jwhitlock/force-en-1490727 bug 1490727: Force en-US for some payments UI
Commit pushed to master at https://github.com/mozilla/kuma https://github.com/mozilla/kuma/commit/b6c2f8458197a64d514de1d863f86af265cfc572 Merge pull request #5059 from potatolondon/add_stripe_customer_id_to_MDN_user bug 1490727: Add stripe customer id to MDN user
Commits pushed to master at https://github.com/mozilla/kuma https://github.com/mozilla/kuma/commit/58288769815fad91857c7ba432a91a3deec3a56b bug 1490727: Anonymize user.stripe_customer_id https://github.com/mozilla/kuma/commit/4f3a25bb4ca02385e4ef0bff196589c2750a5021 Merge pull request #5068 from jwhitlock/anon-stripe-1490727 bug 1490727: Anonymize user.stripe_customer_id
Commit pushed to master at https://github.com/mozilla/kuma https://github.com/mozilla/kuma/commit/45a030074576e0fc762ad7546850fd3bdeeffb91 bug 1490727: Basic recurring payments view (#5061) * Add waffle flag "recurring_payment_beta" for recurring payments * add views and form for recurring payments * add view tests for recurring payments
Commit pushed to master at https://github.com/mozilla/kuma https://github.com/mozilla/kuma/commit/930f8d559557bcc236eb513400d3b630868d7998 bug 1490727: implement recurring payment designs (#5072) * Refactoring form, move Tooltip and forms to separate files. * Implemented designs to existing one-time payment flow. * Integrate back-end with front-end sprint work. * Fix tablet media queries. * Add shadow to form card, design feedback. * Read analytic session store.
Commit pushed to master at https://github.com/mozilla/kuma https://github.com/mozilla/kuma/commit/e060b1570dcf1e9407fc311ad72c77040cf83528 bug 1490727: Recurring payments thank you page styling. (#5073) * Updated styles on the thank you page. * Switch content if it is for recurring payments * Add section on Payment Conditons and links to FAQ. * Add new recurring payment error and success url
Commit pushed to master at https://github.com/mozilla/kuma https://github.com/mozilla/kuma/commit/d4fca21c325c2d51194b9bf99879fc324f4d87c9 bug 1490727: Recurring payments user registration styling (#5080) * Added recurring payment branch to social account signup template * Add alert styling for recurring payment message * Move ``readable-line-length`` style so it can be used for account signup
Commit pushed to master at https://github.com/mozilla/kuma https://github.com/mozilla/kuma/commit/5e0e4de021d9f35bad4c454afd86dccf48faaea6 bug 1490727: add new template for recurring payment thank you email (#5081) Add recurring payment information to thank you email.
Commit pushed to master at https://github.com/mozilla/kuma https://github.com/mozilla/kuma/commit/d61fe8af78ac5e7ff14510e51daf2cbe4a04cda8 bug 1490727: Include confirmation checkbox for recurring payments. (#5082) * initial include of checkbox * add new django form field for terms and conditions, update tests for payments and recurring payments * Merged outstanding changes, updated input styles * Styling checkbox for recurring payment form. * Styling checkbox for recurring payment form. * Cleanup indentation * Address PR feedback, cleanup css * Code cleanup from PR comments. * Remove unessesary relopem attr on link * Fix flake8 linting. * Addredd PR feedback, add validation to checkbox * address PR feedback, added some space for terms validation * Fix style linting * Increase padding around legal copy
Commits pushed to master at https://github.com/mozilla/kuma https://github.com/mozilla/kuma/commit/0e7e681ef840e7cf8e7eb9444a7ef8d960802102 bug 1490727: Americanize "programs" https://github.com/mozilla/kuma/commit/5fa13a7519594aa77dfc09616b320713184dab13 bug 1490727: Update test names, docstrings https://github.com/mozilla/kuma/commit/6e28917f0d10df74a5371659d15c71b8d58bcd77 bug 1490727: Use one-liner mocks Use the return_value parameter to save a line of code. Nice find from @michal-macioszczyk! https://github.com/mozilla/kuma/commit/cb0c1c4b36f74e742805d467d7a3ff53a7a84bd2 bug 1490727: Use same strings in page and email Use the same string formats in the Thank You page and email, so that the paragraph is translated once by volunteers. https://github.com/mozilla/kuma/commit/cff9f5347ac9442315daf48d1ba940b0671a528f Merge pull request #5084 from jwhitlock/payments-nits-1490727 bug 1490727: Fix payments nits
Commit pushed to master at https://github.com/mozilla/kuma https://github.com/mozilla/kuma/commit/b97f548871d4f5e4b49f91ada81ce5b44333c69b bug 1490727: Recurrent payment force GitHub redirect (#5092) **In this PR** https://trello.com/c/SQgMeAXd/11-as-an-anonymous-user-i-want-to-learn-why-i-have-to-log-in-to-github-so-that-i-dont-leave-the-process ** notes for QA ** - [ ] ensure that the recurring payment form cannot be submitted until users login - [ ] ensure one-time payment form still works for both anonymous and authed users - [ ] ensure recurring payment form redirects to github and back to the FAQ page - [ ] ensure form data is preserved **Screenshot** ![screenshot 2018-11-08 at 18 26 08](https://user-images.githubusercontent.com/11092019/48219417-5ff6d400-e384-11e8-9071-812312695317.png)
Commit pushed to master at https://github.com/mozilla/kuma https://github.com/mozilla/kuma/commit/229cac7f59abf21d38f635bc86d23a4e7c0ad021 Merge pull request #5104 from potatolondon/Bug_Error_on_recurring_payment_page bug 1490727: Fixed redirect bug in payments error page
Commit pushed to master at https://github.com/mozilla/kuma https://github.com/mozilla/kuma/commit/5ef6a762dea4336ab7ed9c28e6dae1293695df2d bug 1490727: Update information about subscription cancellation (#5102) * update information about subscription cancellation in thank you page and email * fix spelling mistake in thank you email and page
Commit pushed to master at https://github.com/mozilla/kuma https://github.com/mozilla/kuma/commit/7f3c46170b8f46a53e3a175395734ab7fe7181c5 bug 1490727: Add legal copy for payment terms page. (#5094) * add legal copy for payment term * fixed all requested changes in payment terms legal copy * remove translation templatetag from payments legal copy * remove translation from html tags in payments terms page * update payment terms page with changes made in legal copy document
Commit pushed to master at https://github.com/mozilla/kuma https://github.com/mozilla/kuma/commit/a5f5c5e449808de7a10318c07f775b4c6393be48 bug 1490727: add four new FAQ for monthly payments (#5106) * add four new FAQ for monthly payments * fixed some variable consistency and delete unwanted whitespaces in FAQ on payments page
Commit pushed to master at https://github.com/mozilla/kuma https://github.com/mozilla/kuma/commit/5f3fa91a76bdc6ca08fd38351a3206469f163d5b bug 1490727: include recurring payments on banner (#5101) * add github authentication link for stripe pay button for recurring payment * Updated display to show and hide login prompt * Address PR feedback, document code. * Updated JS doc comment * Address PR feedback. * Address PR feedback remove unused template variable. * Fix isue from bad merge. * Updated logic to switch between payment types. * Fix all merge issues * Alphabetise css rules * fix payment view test * add json versions for onetime and recurring donation choices * Reuse settings vars for donation choices. * Address PR feedback and fix margin issues. * Add `for` attr on label in payment form. * Use array loop shorthand. * Use semantic varible names, not booleans. * Use text-color as input colors * Address feedback, cleanup comments and globals. * Prevent empty class attr. * Fix runtime error on window. * Added blankline end of payments-form.html. * Fix payment type form switch. * Force monthly payments by default. * Fix small window and tablet view. * Fix switch form states losing payment selection bug * Fix styling issues with the form. * Fix form popover initial load amount selection. * Fixed amounts selection being saved when switching form on the popover. * Fix amount switch action. * Prevent double `/month` appearing on FAQ payment page. * Prevent popover init on FAQ page. * Fix initial loading of form to percist amount selection * Include frequency on stripe modal button * Typo in variable name. * Stop validation from running when switching forms. * Fix screenreader label, fix payment link on faq page. * Force collapse when on tablet view with extended banner.
Commit pushed to master at https://github.com/mozilla/kuma https://github.com/mozilla/kuma/commit/c5dcaff13575435c0645f771a82edf16dd47fc97 bug 1490727: Recurring payment analytics implementation (#5105) * Refactor analytic events. * Basic analytic implementation. * Address various PR feedback. * Stop multiple payment events being emitted. * Merge popover changes, send event on recurring payments FAQ page. * Fix linting, cleanup blankline in js. * Address PR feedback, fix payment button context bug. * Prevent FF autocomplete on banner selection.
Commit pushed to master at https://github.com/mozilla/kuma https://github.com/mozilla/kuma/commit/ad0125d74cdc66c513450c2672c0054ea159bd33 Merge pull request #5110 from potatolondon/bug__proposal_for_multiple_subscription_issue bug 1490727: Fix for multiple subscriptions issue
Commit pushed to master at https://github.com/mozilla/kuma https://github.com/mozilla/kuma/commit/4f02ef5c6365103ae171b50fec17f0d7fc79848e Merge pull request #5112 from potatolondon/bug__Account_pre-filling_fullname bug 1490727: Changed to pre-fill payment name only from MDN user fullname field
Commit pushed to master at https://github.com/mozilla/kuma https://github.com/mozilla/kuma/commit/c292231b086661a97dac47d8a4e88ea46f28ea13 Merge pull request #5115 from potatolondon/hotfix/update-recurring-amounts bug 1490727: Update recurring payment amount brackets.
Commits pushed to master at https://github.com/mozilla/kuma https://github.com/mozilla/kuma/commit/a0c437ffd8fa3d7eecdecfc35c31d46517a8b0d9 bug 1490727: Update copy https://github.com/mozilla/kuma/commit/eec7810dfbbd00cc6c9ba656e245a233ae861339 bug 1490727: Fix legal notice Update phrasing, fix the link to the websites privacy notice. https://github.com/mozilla/kuma/commit/0f99769cae3c50e53d0b4602fd1a3796c053e687 bug 1490727: Update amount validation message Update the amount validation message, shown when neither a custom nor pre-selected amount is chosen, to rephrase and to avoid "donation". https://github.com/mozilla/kuma/commit/6bc86159eca2a5b68813ae8c16da3b06d050e503 bug 1490727: Use American English for canceling https://github.com/mozilla/kuma/commit/11b1d02625d12796ad2b128417afc326e819344a bug 1490727: Use sentence case for page titles https://github.com/mozilla/kuma/commit/9a0feea8183e471271ee262a0a130479f5cede84 bug 1490727: Use "subsequent" like other entries https://github.com/mozilla/kuma/commit/2ef2d504129596d865c8586821313ca48e2f4246 bug 1490727: More sentence case for headings https://github.com/mozilla/kuma/commit/141e4aff9754c0b05ab1e82471b12ab306d6f197 Merge pull request #5116 from jwhitlock/copy-updates-1490727 bug 1490727: Launch copy for recurring payments
Commits pushed to master at https://github.com/mozilla/kuma https://github.com/mozilla/kuma/commit/4b876206841211176c08b63785bbb51ce571d1ba bug 1490727: Change text on banner Change text to "Help grow MDN", to avoid donation phrasing. https://github.com/mozilla/kuma/commit/ffa86eb8750305f6bad9f0985324dd999c0c2cf2 Merge pull request #5121 from jwhitlock/grow-mdn-1490727 bug 1490727: Change text on banner
Commit pushed to master at https://github.com/mozilla/kuma https://github.com/mozilla/kuma/commit/0b1c6e1f261ebcb9527fd802324e93cc1d5bf7b1 Merge pull request #5123 from potatolondon/bug__pre-fill_user_fullname bug 1490727: Fix issue with pre-filling fullname in recurring payment form
Commit pushed to master at https://github.com/mozilla/kuma https://github.com/mozilla/kuma/commit/011d66285deac041101ff675909cbb7534d53ca9 bug 1490727: Round floating point amounts to 2 decimal places (#5118) * Round floating point amounts to 2 decimal places, ie 1.2 to $1.20 * fix rounding * Fix js floating point issue. * Fix event values and stripe modal errors. * Remove whitespace
Commit pushed to master at https://github.com/mozilla/kuma https://github.com/mozilla/kuma/commit/a86ce3e3c916758ac68a9574299aa6ed946300a5 bug 1490727: Fix validation for first name input, adjust custom amount input validation. (#5125) Been working on solving some validation issues for the form fields. Primary issue was the users name field not being filled, but I've also made a small adjustment to the custom input field while here to enforce it to accept numerical values. ** in this PR ** - https://trello.com/c/rxWp9MoR/88-add-field-validation-on-your-full-name ** notes for qa ** - [ ] adding a white space should no longer be considered valid for the users name input field. - [ ] whitespace surrounding the name should be removed. ie `_____josh__` should change to `josh` upon focusing out of the input. - [ ] The custom amount input should now only accept numbers. - [ ] custom amount input should increment by 0.01 when adjusting
Commit pushed to master at https://github.com/mozilla/kuma https://github.com/mozilla/kuma/commit/6dd354a2ed82f4721c7f3c685af69918a3667c48 bug 1490727: Prevent recurring payment events being fired if cookies are disabled. (#5129) A bug was spotted when using Safari with browser storage disabled that an error was hit when adding the user's initial authentication level to local storage. The fix is to test if localstorage exists before using it. This PR does that and prevents recurring payment analytic events being sent to preserve the conversion data. **In this PR** - https://trello.com/c/Hm0a7vxm/94-safari-clicking-pay-button-in-the-banner-has-no-effect **Notes for QA** - [ ] ensure when using a browser with storage disabled there is no run time error.
Commit pushed to master at https://github.com/mozilla/kuma https://github.com/mozilla/kuma/commit/1241b0885cea6eca66b553a17c1224f5cea704fa bug 1490727: Manage recurring payments - cancel button. (#5146) Implementing a new feature to allow customers to cancel their recurring subscription on their profile page. This simply calls the Stripe API to cancel the current payment plan. **in this PR** https://trello.com/c/XuSGCflk/33-as-a-user-i-want-to-be-able-to-cancel-my-subscription-from-my-profile-page **images** ![screenshot 2018-11-27 at 10 17 15](https://user-images.githubusercontent.com/11092019/49101908-4c49d980-f26f-11e8-932f-45dc9052e282.png) <img width="1298" alt="screenshot 2018-11-27 at 18 09 02" src="https://user-images.githubusercontent.com/11092019/49102173-06d9dc00-f270-11e8-9178-335e4b7ace77.png"> <img width="1301" alt="screenshot 2018-11-27 at 18 09 14" src="https://user-images.githubusercontent.com/11092019/49102174-06d9dc00-f270-11e8-8954-25aba2b9e4d7.png"> **Notes for QA** - [ ] Ensure subscription link appears if the recurring_payments feature is enabled. - [ ] If the user has a subscription ensure the information (card details/amount) is correct. - [ ] Ensure styling copy and links on the payment management page work and display correctly - [ ] Ensure cancelling a subscription works and returns a success message
Commit pushed to master at https://github.com/mozilla/kuma https://github.com/mozilla/kuma/commit/067e7faa57701c98d0e191c875499483ed07d2d2 bug 1490727: Remove clear field `x` from email input on IE on payments form. (#5151) IE puts an `X` to the right of inputs in order to clear them. This overlaps the `?` help text action on the email field, so we should disable the IE marker for this input. **in this PR** - https://trello.com/c/Vh52EyJj/96-internet-explorer-x-button-displayed-in-email-field-overlaps-the-button **Screenshot of the bug:** ![screenshot 2018-11-29 at 13 13 41](https://user-images.githubusercontent.com/11092019/49224239-ce094680-f3d8-11e8-920d-065d274a8249.png)
Commit pushed to master at https://github.com/mozilla/kuma https://github.com/mozilla/kuma/commit/ba054e85c476f477e68e601657d40646120b5a6c bug 1490727: Added a new set of analytics for recurring payments. (#5147) We're having issues with analytics for recurring payments. The `Recurring payments > success` event has no label. The label is required for conversion rates as it contains the users authentication level. The solution proposed is to create a new event that has the users authentication in the event action - as this seems more reliable. We want to preserve the current setup so have added _Recurring payment v2_ event category that has the user's status in the event action. Also to keep consistency I have added *all* _recurring payment v2_ events (inc banner shown/expanded) to include the users authentication level in the action. With _recurring payment v2_ I have also kept the authenticated/anonymous label for filtering (if it ever decides to work again!) All new events will look something like ```category: Recurring payments v2 action: success - authenticated, success - anonymous, banner shown - authenticated, banner shown - anonymous, etc... label: authenticated, anonymous value: {{amount in pennies, ie 1200}}``` **In this PR** - https://trello.com/c/OLZjfV9d/97-as-a-po-i-want-to-be-able-to-report-on-conversion-rate-so-i-can-gauge-the-success-of-the-recurring-payments-experiment **notes for qa** - [ ] for every recurring payment event two events must be fired. - [ ] events must contain information on the users authentication level
Commit pushed to master at https://github.com/mozilla/kuma https://github.com/mozilla/kuma/commit/d3c729b0e484eb4c3ced9f99388669fb0d6fc744 bug 1490727: Force form to remove custom amount on change. (#5148) On the popover we should not persist the custom amount input. **in this pr** - https://trello.com/c/66tR9Dje/80-ui-banner-only-remembers-custom-amount-vs-faq-pages-dont-remember-either-predefined-or-custom-amounts **notes for QA** - [ ] on the popover banner when switching between amounts we should reset the custom amount input
Commits pushed to master at https://github.com/mozilla/kuma https://github.com/mozilla/kuma/commit/aac58489de3e76ad43108be44f966b277bfdc18e bug 1490727: Adjust payment mgmt UI strings * Change title to "MDN subscription management" * Fix spelling * Use American spelling of canceled https://github.com/mozilla/kuma/commit/e5b7a303f168a7e14db583ed5256b4fc2e83acf0 Merge pull request #5156 from jwhitlock/strings-1490727 bug 1490727: Adjust payment management UI strings
Status: ASSIGNED → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Product: developer.mozilla.org → developer.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.