@blueorangutan ui

@DaanHoogland a Jenkins job has been kicked to build UI QA env. I'll keep you posted as I make progress.

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 19.73%. Comparing base (5e5ae0c) to head (1b04b97).
⚠️ Report is 2 commits behind head on main.

@@             Coverage Diff              @@
##               main   #13981      +/-   ##
============================================
+ Coverage     19.72%   19.73%   +0.01%     
- Complexity    19941    19959      +18     
============================================
  Files          6371     6371              
  Lines        575738   575786      +48     
  Branches      70471    70478       +7     
============================================
+ Hits         113582   113654      +72     
+ Misses       449810   449780      -30     
- Partials      12346    12352       +6     

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

UI build: ✔️
Live QA URL: https://qa.cloudstack.cloud/simulator/pr/13981 (QA-JID-983)

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

🔴 Test Coverage Grade: D — Marginal

Grade Scale

Branch coverage is shown as a secondary signal. Grade is determined by line coverage.
View full Actions run

Dear @DaanHoogland,

Thank you for taking this nomenclature issue seriously and working on a fix. This is also a constant source of confusion in our organization.

Regarding ACS's use of the word "Account," you recently labeled it "New Tenant Account." While this is an improvement, it may still cause some confusion.

Have you considered using "Department" or "Organizational Unit" instead?

Regards,

@daviftorres I agree with your recommendations in the scope of a corporate organization.

But think of a public cloud where each account could represent a single user. AWS also names it accounts. So maybe renaming is not needed. Just decouple accounts from users and don't have them in the same dialog.

@DaanHoogland a few thoughts and observations:

• the add user button does not have any text in it
• now we have "NEW" Tenant Account and "ADD" LDAP Account - that should be named the same
• I'd prefer to remove the user creation from the account creation page. If that is not possible because the first user has to be created we may split that into two areas where the first one does focus on the account and the second one will cover the creation of the FIRST user in the account

@daviftorres I agree with your recommendations in the scope of a corporate organization.

But think of a public cloud where each account could represent a single user. AWS also names it accounts. So maybe renaming is not needed. Just decouple accounts from users and don't have them in the same dialog.

I see your point and makes sense. But I guess there is no size fits all for this case. And the word "account" is misleading. I am fine with what ever @DaanHoogland decide, but I still think we should diverge the attention of the administrator to the user creation page.

@luganofer closed his issue and I am not sure how to continue. He raised a serious design issue which is not in line with the UI fix I am creating here. How do you think we should continue, @ingox @davift ?

@luganofer closed his issue and I am not sure how to continue. He raised a serious design issue which is not in line with the UI fix I am creating here. How do you think we should continue, @ingox @davift ?

Sorry for the confusion – I closed the issue accidentally while trying to reply. It's reopened now.