nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Simple Automation Rule Not Working

Greg

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.

Accepted answers

Greg

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.

All comments

Brant Schroeder

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.

Paloma Fondon Araujo

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

Greg

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:

Greg

Hi @Paloma Fondon Araujo

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!

Brant Schroeder

Do you have multiple service desk projects? Is Employee onboarding in multiple service desks?

Greg

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.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-service-management