Skip to content

feat(onboarding): improve checklist wording and target project visibi…#2806

Merged
jul-dan merged 1 commit into
stagingfrom
feat/onboarding-checklist-wording
Jul 7, 2026
Merged

feat(onboarding): improve checklist wording and target project visibi…#2806
jul-dan merged 1 commit into
stagingfrom
feat/onboarding-checklist-wording

Conversation

@jul-dan

@jul-dan jul-dan commented Jul 7, 2026

Copy link
Copy Markdown
Contributor

Summary

Issue: QOV-2072

  • Reword onboarding checklist steps for clarity: cluster step becomes "Install Qovery" with clearer option labels ("Create a new cluster (Qovery Managed)", "Local Machine"), and the service step now redirects users to their environment overview instead of dropping them straight into the service creation catalog.
  • Add a new "Spec to Prod" use case to the "What are you looking to do?" onboarding step, and widen the "ask for RDE access" end-of-onboarding CTA to trigger on any of the three AI-related use cases (non-tech team, AI workflows, spec-to-prod).
  • Always show the "Target project" field in the create/clone environment modal (disabled in create mode, editable in clone mode) so users know which project their environment will land in.

Screenshots / Recordings

image image image image

Testing

  • Changes tested locally in the relevant Console's pages and Storybooks
  • yarn test or yarn test -u (if you need to regenerate snapshots)
  • yarn format
  • yarn lint

PR Checklist

  • I followed naming, styling, and TypeScript rules (see .cursor/rules)
  • I performed a self-review (diff inspected, dead code removed)
  • I titled the PR using Conventional Commits with a scope when possible (e.g. feat(service): add new Terraform service) - required for semantic-release
  • I only kept necessary comments, written in English (watch for useless AI comments)
  • I involved a designer to validate UI changes if I am not a designer
  • I covered new business logic with tests (unit)
  • I confirmed CI is green (Codecov red can be accepted)
  • I reviewed and executed locally any AI-assisted code

…lity

Rework cluster/service checklist copy for clarity, add the "Spec to Prod"
use case and widen the RDE access CTA to related AI use cases, and always
show (but disable in create mode) the target project field in the
create/clone environment modal.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
@codecov

codecov Bot commented Jul 7, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 41.89%. Comparing base (fd6bc48) to head (9fab9d9).
⚠️ Report is 7 commits behind head on staging.

Additional details and impacted files
@@             Coverage Diff             @@
##           staging    #2806      +/-   ##
===========================================
- Coverage    47.88%   41.89%   -5.99%     
===========================================
  Files         1250      257     -993     
  Lines        26652     7378   -19274     
  Branches      7760     2256    -5504     
===========================================
- Hits         12761     3091    -9670     
+ Misses       11693     3750    -7943     
+ Partials      2198      537    -1661     
Flag Coverage Δ
unittests 41.89% <100.00%> (-5.99%) ⬇️

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.

🚀 New features to boost your workflow:
  • ❄️ 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.

@RemiBonnet RemiBonnet self-requested a review July 7, 2026 14:52
@jul-dan jul-dan merged commit 5fa18bd into staging Jul 7, 2026
13 of 14 checks passed
@jul-dan jul-dan deleted the feat/onboarding-checklist-wording branch July 7, 2026 15:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants