If I trigger Jira automation with a webhook, but do not have a related issue in this webhook, just data, am I not allowed to access {{project.versions.name}} smart value for example?
I have noticed a difference between my 2 automations - one with manual trigger on an issue and second that comes from a webhook without a related issue - it looks like the first one can list the {{project.versions.name}}, but the one without an issue cant.
Is there a workaround for this for the webhook without related issue or should I relate the incoming webhook with a random issue?
Hi @Anna Mjau
Without seeing the details of your actual rule, a couple of things to try are: when the webhook has data referring to an issue...
Kind regards,
Bill
Hi!
In my case the webhook does not have data referring to a specific issue, it is just a trigger with a release major version in webhook data. The automation would then first check if that major version already exists and if not - create it. For the exists check I wanted to use {{project.versions.name}}, but it does not have a value.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for that additional information, @Anna Mjau
When creating a version, you need to know the project. And if you have the project, the REST API endpoints may be used to identify the versions. With Jira Data Center, that endpoint is:
https://docs.atlassian.com/software/jira/docs/api/REST/9.13.0/#api/2/project-getProjectVersions
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.