Skip to content

Conversation

@ankita-akamai
Copy link
Contributor

@ankita-akamai ankita-akamai commented Dec 24, 2025

Description 📝

Add create notification channel page.

Changes 🔄

List any change(s) relevant to the reviewer.

  • Add create channel button for notification channels.
  • Add landing and routing for create page of notification channels.
  • Add a channel-type-select filter and sub-filters specific to channel type - email {Name, Recipients}.
  • Add corresponding schemas, utilties, test cases, update mocks.

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 🗓️

13 Jan 2026

Preview 📷

image image image

How to test 🧪

Verification steps

(How to verify changes)

  • Navigate to alerts tab under monitor.
  • Navigate to Notification Channels tab.
  • Verify Create Channel button is present.
  • Verify clicking on create channel directs to create-channel page.
  • Verify create channel page has a channel-type-select filter.
  • Verify that channel-type-select is selectable and email is an available option.
  • Select email type, verify that two sub-filters appear - Name and Recipients.
  • Type something in Name filter, verify that it accepts the input.
  • Verify selecting/deselecting usernames works in Recipients filter, for the limit, switch to devCloud and verify only selection of 10 is permitted.
  • After typing name, selecting recipients, click on submit, verify a success snackbar appears and user is re-directed to listing page.
  • Open the create flow again, verify that clicking on cancel re-directs user to listing page.
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

@ankita-akamai ankita-akamai marked this pull request as ready for review December 24, 2025 08:19
@ankita-akamai ankita-akamai requested a review from a team as a code owner December 24, 2025 08:19
@ankita-akamai ankita-akamai self-assigned this Dec 24, 2025
Copy link
Contributor

@venkymano-akamai venkymano-akamai left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

PR looks good

@linode-gh-bot
Copy link
Collaborator

Cloud Manager UI test results

🎉 870 passing tests on test run #4 ↗︎

❌ Failing✅ Passing↪️ Skipped🕐 Duration
0 Failing870 Passing11 Skipped44m 32s

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

Projects

Status: Review

Development

Successfully merging this pull request may close these issues.

3 participants