Skip to content

docs: update Jira notification channel documentation - #4114

Draft
revmag wants to merge 1 commit into
mainfrom
docs-sync/batch_20260903_120312
Draft

docs: update Jira notification channel documentation#4114
revmag wants to merge 1 commit into
mainfrom
docs-sync/batch_20260903_120312

Conversation

@revmag

@revmag revmag commented Sep 3, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • Document the new Won't-fix resolution field in the Jira alert channel Advanced Options: entering a Jira resolution name (e.g. Won't Do) makes a re-firing alert open a new issue instead of reopening one closed with that resolution.
  • Note that the match is case-sensitive and must be the exact resolution name from the project's resolution scheme.
  • Clarify precedence: Won't-fix resolution bypasses the Reopen window check entirely.
  • Note the bug fix where editing a channel via the UI now preserves an API-set wont_fix_resolution value.
  • Add wont_fix_resolution to the API request-body reference table.
  • Updated the frontmatter date on the edited file.

Prose-only: PR #12765 merged same-day and the demo lags, so no new screenshots were captured. Feature has no environment gate, so it applies to both Cloud and Self-Host.

Source PRs: #12765

Auto-generated by docs-sync pipeline

Source PRs: #12765
Auto-generated by docs-sync pipeline
@revmag revmag added the PR-docs Label for direct PR to docs label Sep 3, 2026
@vercel

vercel Bot commented Sep 3, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment
Project Deployment Actions Updated
signoz-web Ignored Ignored Preview Sep 3, 2026 12:06pm UTC

Request Review

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

Labels

PR-docs Label for direct PR to docs

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant