feat(notifications): add priority setting for ntfy agent#2306
Open
fallenbagel wants to merge 3 commits intodevelopfrom
Open
feat(notifications): add priority setting for ntfy agent#2306fallenbagel wants to merge 3 commits intodevelopfrom
fallenbagel wants to merge 3 commits intodevelopfrom
Conversation
Added priority option to the notification agent ntfy. fix #2060
Contributor
There was a problem hiding this comment.
Pull request overview
This PR adds a configurable priority setting to the ntfy notification agent, allowing users to select from five priority levels (Minimum, Low, Default, High, Urgent) instead of the previously hardcoded default value of 3. This addresses issue #2060 which requested a priority picker similar to what exists for Gotify notifications.
Changes:
- Added priority field to NotificationAgentNtfy interface with optional number type and default value of 3
- Implemented priority dropdown selector in ntfy settings UI with validation
- Updated ntfy agent to use configurable priority value with fallback to default
- Added documentation for the new priority setting
Reviewed changes
Copilot reviewed 5 out of 5 changed files in this pull request and generated 2 comments.
Show a summary per file
| File | Description |
|---|---|
src/i18n/locale/en.json |
Added translation keys for priority label and validation message |
src/components/Settings/Notifications/NotificationsNtfy/index.tsx |
Added priority field with dropdown selector and Yup validation schema |
server/lib/settings/index.ts |
Added priority field to NotificationAgentNtfy interface with default value |
server/lib/notifications/agents/ntfy.ts |
Updated to use configurable priority from settings with fallback |
docs/using-seerr/notifications/ntfy.md |
Added documentation section explaining the priority setting |
Comments suppressed due to low confidence (1)
src/components/Settings/Notifications/NotificationsNtfy/index.tsx:72
- The error message for topic validation is using the URL validation message key instead of the topic validation message key. Should use
messages.validationNtfyTopicinstead ofmessages.validationNtfyUrl.
.required(intl.formatMessage(messages.validationNtfyUrl)),
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
gauthier-th
approved these changes
Jan 16, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Adds a configurable priority setting to the ntfy notification agent. Users can now select a priority level (Minimum, Low, Default, High, Urgent) from the ntfy settings page, instead of the previously hardcoded default value. This allows users to control how ntfy handles notification delivery and display.
How Has This Been Tested?
Screenshots / Logs (if applicable)
Checklist:
pnpm buildpnpm i18n:extract