You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.
View groupJoin the community to find out what other Atlassian users are discussing, debating and creating.
I am testing automation and have created a simple automation rule that is supposed to open a new task in the IT Service Project when a new issue is created in the HR Service Project.
Although the rule executes, the task is never opened within the IT Service Project.
Any advice or insight would be greatly appreciated.
Received this helpful solution from Jira Support. Leaving it here in case anyone else comes across this same issue:
For your case, you will need to use the Advanced Compare condition to match the Employee Onboarding request type.
This is a particularity of NextGen Service projects which treats request types as issue types. For this reason, automations will not match the Request Type field.
What is in the audit log? Even though the automation ran criteria may have not been met or another error could have occurred preventing the automation from working.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The Audit Log states that 'No actions performed' because the request did not meet the Condition. The (single) condition is that the new request should be of the Request Type: Employee Onboarding and it is:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Do you have multiple service desk projects? Is Employee onboarding in multiple service desks?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Greg
Could it be that you need to create a global automation rule to include in the scope both projects, the source and the destination of the Issue that should be created automatically?
I hope it helps you.
Greetings
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Great insight. I changed the scope of the rule to run across all projects (Global Rule), however the result is still the same. The log is stating that the condition is not being met.
Thanks for your tip though!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Connect with like-minded Atlassian users at free events near you!
Find an eventConnect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.
Host an eventYou're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.