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; } } }

Problem with approvals

John Black

I have a simple ticket type with approval

If I create a ticket for this ticket type manually everything works fine and the approver gets an email to approve

However I need to create a ticket using Project Automation

When I create exactly the same ticket with the same approver the approver don't get an email. When I check the ticket I see that it's in the Waiting for approval stage and the correct person is listed as the approver. If this person goes to the Customer Portal - Approvals he doesn't see that he supposed to approve something. Also If I check Customer Notification Approvals log I see that there is Error for this ticket. However there are no details there regarding what is the error.

I tried to add an Intermediate stage before approval stage, but when I transition from Intermediate to the approval stage Approval still doesn't work.

Any idea what could be wrong ?

Accepted answers

Marini Marini_oy8r62

Hi @John Black

To further investigate the issue, can you please share a screenshot of your automation rules?

Thanks,

Marini

All comments

Marini Marini_oy8r62

Hi @John Black

To further investigate the issue, can you please share a screenshot of your automation rules?

Thanks,

Marini

John Black

Hi @Marini Marini

This is the rule

Here you you can see the ticket that gets created. It is assigned to me as approver as it should. But I don't get approver notification and if I go to Customer Portal - Approvals its not there

This is the workflow for this ticket type

This is an error from Customer Notification Approvals log

Marini Marini_oy8r62

Hi @John Black

Jira Service Management (JSM) works a little bit different from Jira Software (JSW):

Every JSW issue is tied to an Issue Type
BUT in JSM, every JSM issue MUST be tied to a Request Type. A Request Type is tied to an Issue Type

If the IS-583 is created by the Automation Rule, I believe, if you click "Service project request" on the right-side menu, you will see "No match" for the Request Type field.

That's because, in your automation rule, you use Actions to "Create issue" where you won't be able to select the "Customer Request Type". By right, you should select Actions to "Create Service Management request" and select the correct Request Type.

If a JSM issue is created without a valid Request Type, the issue will not behave like a JSM Issue such as:

The issue will not be available from the portal. Thus, the approver will not be able to get an approval notification from the portal
The approval workflow will not work properly. For example, the approver will not get an email notification

My recommendation:

When working with JSM issues, always tie an issue with a Request Type. Most of the time, you do not need to care about the Issue Type
Modify your automation rules. When creating a JSM issue, use Actions "Create Service Management request" so that you can select the appropriate Request Type
When doing your testing, use different users for different roles such as Assignee, Reporter, or Approver. This way, you will mimic a real-case scenario

I hope the above answer helps!

Regards,

Marini

Welcome!

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

Quick Links

Find more posts tagged with

server

jira

approver

jira-service-management

jira-service-management-server