Assigning tickets to service desk reporters seems to prevent customer notifications
Asked by Rob vanSpronssen:

I have found that if my workflow for a support incident assigns a ticket to a reporter (i.e. someone who ONLY has portal access, and does not have a Jira license), then customer notifications stop working entirely until the assignee changes back to a user with a Jira license (one of our service desk agents).

For example, when we find we need more information from the customer, we move the status from Assigned to Pending. At that point the SLA pauses, and it becomes a customer (reporter) action to respond. So it makes logical sense (to me!) to have the workflow assign the ticket to the customer (reporter). But if the workflow does that, the customer does not get a customer notification that the status changed to Pending.

I have noticed that as soon as the assignee changes back to a service desk agent (with Jira license), the customer notifications to the customer (reporter) work just fine on status change or any other condition as configured in Customer Notifications.

A nice side effect of assigning tickets to a customer (reporter) is that they show up on the Service Desk board under the list of assignees, making it easy to filter on a particular customer, to see what is in their "action" queue.

So my question is this: why does assigning a ticket to a customer (reporter) who has no Jira license seem to prevent a customer notification of the change in status?


Answers:
author: Nadhila Savira
body: Hi Rob,

I want to clarify a bit here: when you say "assign tickets to a reporter", do you mean that the Assignee and Reporter becomes the same user?

If that is the case, our system would **not** recognise the Reporter as a customer anymore, and thus it will indeed prevent Customer Notifications from being sent. This is because the Assignee is meant to be your staff members, people working on your tickets.

If the Assignee is your customers, they would also not be able to do things an Assignee is supposed to be doing, since a true Assignee does indeed require JSM license.

Just so you know also: if your customers are added as Assignee, they will get your internal notifications configured under **Project Settings \> Notifications**, which might contain some extra information you may not want to display to your customers.

Hope this clarifies the events you're seeing here.

comments: author: Rob vanSpronssen
body: Thank you for the response.

Yes, the Assignee and Reporter become the same user. This is done by a post function of the transition when the action is on the customer. I get no error indication from the post function upon this assignment (but perhaps I just don't know where to look for it?)

The portal is a back and forth communications mechanism between customers and agents. Since it is possible to expose transitions to the portal, in fact the customer is working on tickets, at least in a limited manner.

It would not make sense to send internal notifications to our customer, so I appreciate that I simply cannot make a customer an Assignee.

It would be nice to somehow be notified of this inappropriate assignment, rather than just observing that Customer Notifications stop functioning for "unknown" reasons.

Thanks again


author: Joseph Chung Yin
body: [@Rob vanSpronssen](/t5/user/viewprofilepage/user-id/4672421) -

In general, only users with Agent licenses in JSM can be assigned to issues. Can you provide more information on why you want to assign issue to the customer (reporter) of the issue?

I am surprised that your WF didn't error out since (by default) only members of Project's Service Desk Team role or Administrators role can be "assigned" with issues when you access your project's permission scheme configuration.

I would highly recommend that you utilize WF statuses and setup appropriate queues to manage your issues in this specific case. You shouldn't be assigning issues to non agents users because JSM will not work properly as expected.

Hope this helps and provide your inputs.

Best, Joseph Chung Yin

comments: author: Rob vanSpronssen
body: Thanks for the response.   

See "the nice side effect" in my post as to why I want to do this.   

My workflow did not error out. It happily assigned the ticket to the reporter. But I see you cannot manually assign the ticket to a reporter. That's what I tweaked on to see if this was why the Customer Notifications abruptly stopped working when the workflow did the assignment.   

I researched many Atlassian articles about Customer Notifications. None I found mentioned that this condition would cause them to stop.   

Is there a workflow log file that I can inspect for such errors? It did not show up in the Service Desk email exceptions log, which was the natural place to look because that was the feature that stopped working.   

Thank you.


author: Joseph Chung Yin
body: [@Rob vanSpronssen](/t5/user/viewprofilepage/user-id/4672421) -

Can you clarify which customers notification event(s) failed?

In addition, what board are you referring to in your nice side effect? I am assuming you are not referring the display in the Portal UI? Lastly, who is using the board?

"A nice side effect of assigning tickets to a customer (reporter) is that they show up on the Service Desk board under the list of assignees, making it easy to filter on a particular customer, to see what is in their "action" queue."

Can you also verify what is being called out in your project's permission configuration scheme under "Assignable users" permission?

Lastly, you will need to contact Atlassian Support (<https://support.atlassian.com>), so they can access the logs in the backend for you.

Best, Joseph


author: Rob vanSpronssen
body: Thanks, here are answers to your questions.

Customer notifications that failed when the Assignee was a customer (reporter):

* public comment added, edited
* resolved
* customer-visible status changed

I did not try user participant added or organization added but they likely would also have failed. The only notifications that worked was when the customer changed the status to closed or re-opened on the portal. I presume that worked because the workflow unassigned the ticket (closed) or assigned it to a Jira licensed user (re-opened) in a post function. The clear pattern was as long as the assigned user was a customer (reporter) with no Jira license, all Customer Notifications failed.

The board is the display in the portal UI. Its the only board I am aware of that is associated with the service project. Our internal service desk agents use it (with Jira licenses):

![ServiceDeskBoard.png](https://community.atlassian.com/t5/image/serverpage/image-id/347465i78F4F5A00E011B0D/image-size/large?v=v2&px=999 "ServiceDeskBoard.png")

When there were tickets assigned to reporters, they showed up in the list of assignees, so we could pick one or more of them to see which issues were on their plate. Worked very nicely (but have this assignment caused Customer Notifications to stop working).

This is our Assignable Users from the permission scheme:

![AssignableUsers.png](https://community.atlassian.com/t5/image/serverpage/image-id/347466iBD54EE1023148726/image-size/large?v=v2&px=999 "AssignableUsers.png")

Thanks again.


author: Rob vanSpronssen
body: PS. Queues work great, but they do not have a "slice and dice" capability that users can interact with like the board does. A board is much more functionally useful for analyzing the tickets in motion. Queues are great for seeing particular slices, but only one slice at a time.


author: Rob vanSpronssen
body: PPS. If I added a Project Role (Service Desk Customers) to the Assignable User permission in our permission scheme would this allow the assignment to Service Desk Customers AND (most importantly) not cause Customer Notifications to fail? That would be a great solution for this issue, but I would want to limit this to the support project, as these users should not be assignable to tickets in our other Jira projects.

I tread very carefully in the permission scheme...

Thanks


author: Joseph Chung Yin
body: [@Rob vanSpronssen](/t5/user/viewprofilepage/user-id/4672421)

Adding Service Desk Customers to your permission scheme for the specific project's Assignable User permission may work. You need to ensure that your Support project has its own custom permission scheme, so other projects are not impacted.

Again, I have not experience this type of assignment/change while working with JSM projects. You may still want to reachout to Atlassian Support for their assistance.

If my suggestions helped you, please click on Accept answer when you have a chance, so others with similar asks will see this posting as an answered one.

Good luck.

Best, Joseph


author: Rob vanSpronssen
body: Thank you for your time!


author: Rob vanSpronssen
body: I will contact Atlassian support to see if there is a definitive answer before I do anything with the permission scheme.

Thanks again,

Rob


Tags: cloud

jira-service-management

jira-service-management-cloud