Skip to content

Update success banner to account for async operation

What does this MR do and why?

Describe in detail what your merge request does and why.

Screenshots or screen recordings

Screenshots are required for UI changes, and strongly recommended for all other merge requests.

Screenshot_2022-09-02_at_22.24.01

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

  1. Make sure CustomersDot is running. See steps here.
  2. Make sure your gdk is running with GITLAB_SIMULATE_SAAS=true
  3. Visit Billing path of a group (e.g., http://localhost:3000/groups/flightjs/-/billings)
  4. Pick a Plan and click on update
  5. Complete the purchase
  6. You should be redirected to the Billing path (e.g. http://localhost:3000/groups/flightjs/-/billings?purchased_quantity=10&plan_id=ultimate)

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

Related to #364153 (closed)

Edited by Angelo Gulina

Merge request reports