Jira for workflows connection settings not allowing URL (max 50chars...)

SjoerdB — Thu, 30 Jan 2025 08:43:03 GMT

Hi,

I'm setting up a Jira connection at my customer, and am running into an issue with the length of the webhookurl.

I can create a "fake" connection definition when I use a short URL, but as soon as I paste the atlassian webhook URL that is generated for my project, I get an error indicating: "Name has to be between 1 and 50 characters long".

At first I thought this was just a UI bug, but also the API returns this message as soon as the URL exceeds 50 chars.

Is there any way currently I can push my definition without getting this check/error? Because I cannot change the webhook URL delivered by Atlassian-Jira.

Thanks!

Sjoerd

PS. the fact that the message is "Name..." instead of "URL...." makes me wonder if it is not just a very simple bug in assigning checkrules to api fields

...
...
"error": {
  "code": 400,
  "message": "Constraints violated.",
  "constraintViolations": [
  {
    "path": "app:dynatrace.jira:connection/0/url",
    "message": "Name has to be between 1 and 50 characters long",
    "parameterLocation": "PAYLOAD_BODY",
    "location": null
  }
  ]
},
....
....

Re: Jira for workflows connection settings not allowing URL (max 50chars...)

christian_kreuz — Wed, 05 Feb 2025 16:53:00 GMT

Jira for Workflows does not support Webhook URLs. The only supported authentication methods are: Basic Authentication, Personal Access Token, Jira API Token.

All three of those require an URL that looks like this: https://{environment}.atlassian.net (for SaaS) or https://jira.somehost.com (for Jira Data Center / on-prem).

topic Jira for workflows connection settings not allowing URL (max 50chars...) in Automations

Jira for workflows connection settings not allowing URL (max 50chars...)

Re: Jira for workflows connection settings not allowing URL (max 50chars...)