Holger Waschke

It´s a breaking change but it probably makes more sense this way. You can set update_description and update_summary in the config default section and may override it per receiver as...

for better clearness we use multiple templates, e.g. one template per jira custom field. as we use templates for mapping they get quite big and its handy to separate them....

customfield generated out of template does not gets interpreted as an array

1

I have a customfield 23210. If I pass is statically as an array `[{'key':'PSK-713555'},{'key':'PSK-953155'}]` it works just fine, if i pass it trough the template the output is exactly the...

jira integration template customfields

2

We using templates to fill the jira customfields, e.g. ``` {{- define "asp.priority" -}} {{- with index .Alerts 0 -}} {{- if .Labels.severity -}} {{- if eq .Labels.severity "disaster" -}}...

Jira Integration: Allow configuring issue update via parameter

15

This change allows disabling the update of issue descriptions. It´s a non breaking change the default is still to update everything. Only if you set the parameter disable_update_description explicit to...

feat(Jira Integration): use grouplabels to calculate hash

20

**Problem** The hash used to identify existing Jira issues is not unique across multiple Jira projects. **Root Cause** Currently, the hash is generated using the ExtractGroupKey function, which relies on...

this resolves https://github.com/prometheus/alertmanager/issues/4585 Description has to be of type any in the struct to be able to parse it as string (for api v2) or as rawJSON (for api v3)...