Is there an existing issue for this?

• I have searched the existing issues

What happened?

Description

It seems that the jiraConfig struct defined in https://github.com/prometheus-operator/prometheus-operator/blob/main/pkg/alertmanager/types.go#L431 is missing send_resolved parameter, which is mentioned in documentation (https://prometheus.io/docs/alerting/latest/configuration/#jira_config).

Steps to Reproduce

Add send_resolved boolean parameter to entry in receivers[].jira_configs[] of Alertmanager configuration.

Expected Result

Adding send_resolved parameter in jira_configs entry shouldn't lead to an error.

Actual Result

Operator will report an error during unmarshaling jiraConfig struct.

Prometheus Operator Version

0.81.0, but according to code 0.84.0 also has this issue

Kubernetes Version

1.32.5

Kubernetes Cluster Type

kubeadm

How did you deploy Prometheus-Operator?

helm chart:prometheus-community/kube-prometheus-stack

Manifests

prometheus-operator log output

ts=2025-08-01T14:15:51.137080256Z level=info caller=/workspace/pkg/alertmanager/operator.go:546 msg="sync alertmanager" component=alertmanager-controller key=prometheus/prometheus-kube-prometheus-alertmanager
ts=2025-08-01T14:15:51.141319002Z level=error caller=/workspace/pkg/operator/resource_reconciler.go:557 msg="Unhandled Error" logger=UnhandledError err="sync \"prometheus/prometheus-kube-prometheus-alertmanager\" failed: provision alertmanager configuration: failed to initialize from secret: yaml: unmarshal errors:\n  line 48: field send_resolved not found in type alertmanager.jiraConfig"

Anything else?

No response