Forum Discussion

Jeroen_Gouma's avatar
Jeroen_Gouma
2 years ago

Variable json content in http integration

Hi all, we implemented custom http integration to create tickets in Jira Servicedesk. This works fine. However, new requirement is to put a variable (##jira.assetid##) in the content to link the ti...
custom http
http
integration
  • Mike_Moniz's avatar
    Mike_Moniz
    2 years ago

    When you say that integration fails, do you mean that LM doesn’t sent the REST request at all? Or that Jira is rejecting the json you are passing? I thought that LM will just fill in unset tokens with nothing, aka send over  "customfield_10500": [] . If you are looking to have some sort of default value when it’s not set, I would suggest setting a jira.organizationid property on the root folder/group as a default and let sub groups override it.

    I don’t use Jira so I might not understand the situation fully. I’m assuming jira.organizationid is assigned to groups/resources and not pulled from somewhere else.

Anonymous's avatar
Anonymous
2 years ago

Completely agree and we need this too. Currently every integration we have has to be configured at least twice in LM, once for regular alerts and once for collector down notifications. These two notifications do not have a common set of alert tokens, so the payloads have to be drastically different. Having the ability to use a templating engine like Jinja2 would allow for conditional branching and also other options.