Add new Jira search endpoint with new api_type option and auto detect

[cjedro]

closes #4513

i followed #4513 (comment)

maybe api_type = datacenter should not override host *.atlassian.net but lets discuss

also, as in the comment, only overriding the search api version for now

[jkroepke]

Hi @cjedro thanks for your PR.

I wrote some comments, maybe we can avoid having 2 structs and the different API endpoints is just sufficient.

No idea, why Expand was a list before, because in API docs, the mentioned as string as well. However we do not use Expand anyways.

[cjedro]

@jkroepke thanks so much for the review, I will work on your recommendations later today or tomorrow

[jkroepke]

Consider to add the default value to

alertmanager/config/notifiers.go

Line 198 in d563660

DefaultJiraConfig = JiraConfig{

Consider to add a validation for the values here

alertmanager/config/notifiers.go

Line 920 in d563660

func (c *JiraConfig) UnmarshalYAML(unmarshal func(any) error) error {

similar to here:

alertmanager/config/notifiers.go

Lines 833 to 837 in d563660

	if c.ParseMode != "" &&
	c.ParseMode != "Markdown" &&
	c.ParseMode != "MarkdownV2" &&
	c.ParseMode != "HTML" {
	return errors.New("unknown parse_mode on telegram_config, must be Markdown, MarkdownV2, HTML or empty string")

[chrko]

The requested/recommended DefaultConfig part is missing (#4542 (comment))

Consider to add the default value to

alertmanager/config/notifiers.go

Line 198 in d563660

DefaultJiraConfig = JiraConfig{

[cjedro]

@jkroepke, @chrko i added the things discussed here.
Besides this i talked to @jkroepke and he recommended to leave out the global jira api type so i removed it, if we want to keep it i'm happy to re-add for sure

is someone aware why the tests are failing? i found this in the logs
time=2025-09-11T11:46:46.762Z level=ERROR source=main.go:559 msg="Listen error" err="listen tcp 127.0.0.1:39549: bind: address already in use"

[jkroepke]

LGTM

[jkroepke]

Hey @sysadmind could you do a second look?

• And no idea about circle ci. Seems like a flasky test.

[cjedro]

Hey @sysadmind could you do a second look?

• And no idea about circle ci. Seems like a flasky test.

it worked now..

[sysadmind]

The tests are flaky with circleci. You can just run them again. I have a PR open to add the mail tests back to github actions so that we can fully move.

[dinwath]

Hi, is there any planned date to release this feature? we would like to integrate jira with our alerting workflow but we're currently struck due to Atlassian change of API in Jira Cloud

[cjedro]

@dinwath at least the Release is getting prepared: #4586

[jkroepke]

Should be part of https://github.com/prometheus/alertmanager/releases/tag/v0.29.0-rc.1