Skip to content

Budget wording - Azure project submission - remove AWS cost related checkbox - Edit AWS budget wording #5620

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

Open
ThibaultBC opened this issue May 8, 2025 · 1 comment
Assignees

Comments

@ThibaultBC
Copy link

ThibaultBC commented May 8, 2025

As a Customer, I want a submission pop-up that shows the right information about Azure, so that I am not confused by seeing AWS related costs.

Context: There's a leftover AWS info checkbox when submitting a project set, that is also showing for Azure and should not. There is a baseline cost for AWS, but it doesn't apply to Azure. See screenshot below:
Screenshot 2025-05-05 at 2.47.58 PM.png

Acceptance Criteria:

  1. When MS Azure is selected, and the user submits a project provisioning request, the Pop-up should NOT display the second checkbox. It can simply be removed.
  2. That checkbox remains for AWS.
  3. In the case of AWS, change the wording to "... liable to pay the base charge of USD 50 to USD 75 per account, up to around USD $200 to $300 when 4 accounts are created for this project set."
    3.1 This is to be consistent with the lighter project set option, which allows clients to create either 1, 2, 3 or 4 accounts.
  4. To be consistent with the other existing info box in the project budget section, please edit that box wording (see screenshot below) with the following text: "There will be a base charge of USD 50 to USD 75 per account, up to around USD $200 to $300 when 4 accounts are created for this project set."

Screenshot 2025-05-08 at 1.42.14 PM.png

@Iryna-Kaplun
Copy link
Collaborator

Iryna-Kaplun commented May 8, 2025

Thibault's comment:

Removing the AWS budget checkbox when an Azure project is selected is the most important one - it gives a wrong indication. Not a bug but user logic issue. Since it "only" requires removing an existing checkbox conditionally, I'd suppose it's a relatively low effort - but I'll let you determine that - and would be the only one I put as a medium/high priority.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants