docs: document strict Jira and incident.io Site URL validation - #4122
Draft
revmag wants to merge 1 commit into
Draft
docs: document strict Jira and incident.io Site URL validation#4122revmag wants to merge 1 commit into
revmag wants to merge 1 commit into
Conversation
Source PRs: #12772, #12644 Auto-generated by docs-sync pipeline
|
The latest updates on your projects. Learn more about Vercel for GitHub. 1 Skipped Deployment
|
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
1 participant
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
The Jira notification channel now strictly validates the Site URL: trailing slashes and surrounding whitespace are rejected with an explicit error instead of being silently trimmed. The same rule already applies to the incident.io Alert source URL (shipped with its integration) but was undocumented.
jira site must not end with a trailing slash,jira site must not have leading or trailing whitespace).dateon both edited files.No screenshots: backend validation change with no new UI controls.
Not a breaking change for existing configs: the previous code normalized and stored the trimmed URL, so saved values are already canonical and read back fine. Only a new save with a non-conforming URL now fails.
Issues closed by this PR
Source PRs: #12772, #12644
Auto-generated by docs-sync pipeline