[pull] main from SigNoz:main - #947
Merged
Merged
Conversation
…2488) #### Description Adds **Jira** and **JSM Ops** as alert channel types in the existing channel flow. No new pages or endpoints — both reuse the same create / edit / list / test actions as every other channel. **Jira** - Required fields: Jira Cloud site URL, Atlassian email + API token, project, and issue type. **Summary** and **Description** are prefilled, editable templates (the rich issue body is built server-side). - The form recommends using an Atlassian **service account**, with a link to the docs. - Advanced Options: priority, labels (chip input), resolve/reopen transition-name overrides, and the reopen window. - Client-side validation mirrors the backend (must be an `https://….atlassian.net` URL; reopen window ≥ 1m) purely for a friendlier error — the backend enforces the same rules. **JSM Ops** - The JSM **integration API key** is the only required field — there is no site or region to configure. - **Message**, **Description**, and **Priority** are prefilled, editable templates; **Tags** is a chip input (defaults to `signoz`). **Shared behaviour** - `Send resolved alerts` is on by default; on resolve, Jira transitions + comments the issue and JSM Ops closes the alert. - Optional fields left empty are omitted from the payload, so the backend applies its own defaults. - Jest tests cover both forms: rendering, prefilled defaults, validation errors, and the exact save payloads (`jira_configs` / `jsmops_configs`). - Generated API client types are regenerated to include `jsmops_configs`; locale strings added for all new fields. #### Issues closed by this PR Stacked on top of #12478 · Discussion: SigNoz/pulse-pod#169 · Closes SigNoz/pulse-pod#170 #### Screenshots / Screen Recordings Jira Form : <img width="1512" height="823" alt="Screenshot 2026-08-18 at 1 16 49 PM" src="https://github.com/user-attachments/assets/1a3a3419-de1b-4bf1-8a71-50d8341e5d47" /> Expanded Jira advanced options : <img width="1444" height="406" alt="Screenshot 2026-08-18 at 1 17 08 PM" src="https://github.com/user-attachments/assets/d1298009-b0f3-4f3d-b960-b805b12f5026" /> JSM Ops Form: <img width="1479" height="631" alt="Screenshot 2026-08-18 at 1 19 11 PM" src="https://github.com/user-attachments/assets/678b130b-8b1f-41c8-a78a-b6bd58ae2904" /> JSM Ops Advanced Options: <img width="1455" height="239" alt="Screenshot 2026-08-18 at 1 19 22 PM" src="https://github.com/user-attachments/assets/a4425b39-b7e1-4f10-bd0a-83dbc678693a" /> #### Additional Information Notes for reviewers: - **This branch is stacked on #12478**, so the diff shows the backend commits too — only the `frontend/` files are new here. - Follows the pattern of the Google Chat channel frontend. - **JSM Ops seeds `send_resolved: true` in its prefilled config on purpose** — the backend cannot default it to on, so the UI carries the default and sends it explicitly. - **Tags is a chip input in the UI, but the backend takes a comma-separated string** — joined on save, split back into chips on edit-prefill. - Jira's reopen window is sent as a duration string (`"72h"`) even though the generated DTO types it as a number, so it's cast at that one boundary. `custom_fields` stays API-only and is not surfaced in the form. --------- Co-authored-by: Naman Verma <naman.verma@signoz.io>
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
See Commits and Changes for more details.
Created by
pull[bot] (v2.0.0-alpha.4)
Can you help keep this open source service alive? 💖 Please sponsor : )