Skip to content

Conversation

@grevanak-akamai
Copy link
Contributor

@grevanak-akamai grevanak-akamai commented Dec 23, 2025

Description 📝

Apply suggested UX changes in networking section to ease the Linode create flow.

Changes 🔄

  • Change selection card to radio selection for network connection under networking section in create linode flow
  • Remove description for each of the network interface type and show it in info icon.

Scope 🚢

Upon production release, changes in this PR will be visible to:

  • All customers
  • Some customers (e.g. in Beta or Limited Availability)
  • No customers / Not applicable

Target release date 🗓️

NA

Preview 📷

Before After
Screenshot 2025-12-23 at 5 27 35 PM Screenshot 2025-12-23 at 5 28 02 PM
Screenshot 2025-12-23 at 5 28 22 PM Screenshot 2025-12-23 at 5 28 34 PM

How to test 🧪

Prerequisites

  • Navigate to create Linode flow and scroll to networking section

Verification steps

  • Ensure new design changes are reflecting to show radio selection for network connection type instead of selection cards
  • Ensure descriptions are not shown and instead an info icon with tooltip message is shown for each network interface type.
Author Checklists

As an Author, to speed up the review process, I considered 🤔

👀 Doing a self review
❔ Our contribution guidelines
🤏 Splitting feature into small PRs
➕ Adding a changeset
🧪 Providing/improving test coverage
🔐 Removing all sensitive information from the code and PR description
🚩 Using a feature flag to protect the release
👣 Providing comprehensive reproduction steps
📑 Providing or updating our documentation
🕛 Scheduling a pair reviewing session
📱 Providing mobile support
♿ Providing accessibility support


  • I have read and considered all applicable items listed above.

As an Author, before moving this PR from Draft to Open, I confirmed ✅

  • All tests and CI checks are passing
  • TypeScript compilation succeeded without errors
  • Code passes all linting rules

@grevanak-akamai grevanak-akamai requested a review from a team as a code owner December 23, 2025 12:05
@grevanak-akamai grevanak-akamai marked this pull request as draft December 23, 2025 12:08
@grevanak-akamai grevanak-akamai force-pushed the feature/UIE-9863-ux-changes-in-linode-create-flow branch from 8aa1986 to bebb059 Compare December 23, 2025 12:40
@grevanak-akamai grevanak-akamai added UX/UI Changes for UI/UX to review Linodes Dealing with the Linodes section of the app labels Dec 23, 2025
@grevanak-akamai grevanak-akamai marked this pull request as ready for review December 23, 2025 15:26
@dabaka
Copy link

dabaka commented Dec 23, 2025

Is the beta tag being removed in all flows?

@bnussman-akamai bnussman-akamai added the Related Cypress Test Failure Test failure(s) are the result of changes in this PR and must be addressed before merging. label Dec 23, 2025
@grevanak-akamai grevanak-akamai force-pushed the feature/UIE-9863-ux-changes-in-linode-create-flow branch from bebb059 to 73cc329 Compare December 29, 2025 06:07
@grevanak-akamai grevanak-akamai requested a review from a team as a code owner December 29, 2025 06:07
@grevanak-akamai grevanak-akamai requested review from dmcintyr-akamai and removed request for a team December 29, 2025 06:07
@linode-gh-bot
Copy link
Collaborator

Cloud Manager UI test results

🔺 1 failing test on test run #4 ↗︎

❌ Failing✅ Passing↪️ Skipped🕐 Duration
1 Failing869 Passing11 Skipped42m 46s

Details

Failing Tests
SpecTest
clone-linode.spec.tsCloud Manager Cypress Tests→clone linode » can clone a Linode from Linode details page

Troubleshooting

Use this command to re-run the failing tests:

pnpm cy:run -s "cypress/e2e/core/linodes/clone-linode.spec.ts"

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

Labels

Linodes Dealing with the Linodes section of the app Ready for Review Related Cypress Test Failure Test failure(s) are the result of changes in this PR and must be addressed before merging. UX/UI Changes for UI/UX to review

Projects

Status: Review

Development

Successfully merging this pull request may close these issues.

4 participants