Hi Atlassian group,
I have created some automations for my project that trigger the transition of a ticket status, updating fields.
The rules work perfectly, the author is 'Automation For Jira' and the project role 'atlassian-addons-project-access' is associated with each permission of the Permission Scheme (associated with the project).
I have added custom (user defined) events with 'Issue Moved' model to the notification scheme associated with the project, because I want to notify a particular group of people for a particular state transition of some tickets.
But I have the following problem:
- if in the post-functions to the transition of the workflow I use a system event (Jira defined), at the change of state the automations work perfectly, and even the notifications arrive correctly.
- on the other hand, if in the post-functions at the transition of the workflow I use a custom event (user defined), at the change of state the automations DO NOT work anymore, but the notifications arrive correctly.
I tried to change actor and flag the 'Allow rule trigger' option to the automations but nothing has changed.
I don't know where the problem is.. are there missing permissions that I'm not seeing?
Thank you for the help.
Automation for Jira rely on the specific events coming from Jira to differentiate what types of triggers can be fired. At the current time, Custom events from Jira workflows aren't emitted to other add-ons so we can't react on them
Sorry about that but you'll need to use Generic Events
even if I already imagined this could be the answer, thanks anyway.
For now I resolved with the external app Jira Misc Workflow Extensions (JMWE), with which fortunately I can trigger the sending of custom notifications and keep the automation rules respected.
Calling all collaborators and Confluence users! Our Appy Hours event on September 29th features 4 presenters demoing functionality to superpower Confluence. Don't miss learning about these apps i...