Skip to content

Conversation

@moreamazingnick
Copy link

  • Introduces a Prefix for the icingaKey
  • encloses the $keyfield so Jira Fields with spaces can be used as icingaKey.

This will not break with existing jira tickets if the prefix is not set at all.

Of course if the prefix is set older tickets can not be found.

Best Regards
Nicolas

@cla-bot cla-bot bot added the cla/signed label Sep 18, 2025
@nilmerg
Copy link
Member

nilmerg commented Oct 27, 2025

Sorry that it took so long to look at this.

Now, if you want to get the quote fix in the next release, please split this into its own pull request this week.

As the prefix you want to introduce is somewhat questionable if you ask me. Why should the user be responsible to configure this? With Icinga DB there is the environment ID and since the key field isn't visible anyway, it doesn't hurt it being a hex-encoded binary string. So to me this is just a checkbox whether to respect multiple environments or not. Of course, plus an option (not necessarily in the UI) to also designate the current Icinga Web JIRA Integration should also be responsible for tickets without any environment attached. But this is out of scope for the next release, I'm sorry.

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants