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

Change status after every customer reply

Gui Ávila

Hi,

As far as I know, the default JSM workflow automatically works this way: when the customer makes a new comment, the status changes to satus "Waiting for support", something like that.

I don't know what cause the problem, but now this behaviour is not happening anymore. Customers add new comments, and the status does not change.

Please, how can I fix that? I think I could use automations as a workaround, but this used to work out of the box, no automations required.

Thanks,

Gui.

Accepted answers

Jack Brickey

is the status in "Waiting for customer" at the time the customer makes the comment? Please check your automations because this is where the transition on comment will occur. Check both New and Legacy areas.

All comments

Jack Brickey

Gui Ávila

Not sure I understand what you said @Jack Brickey .

Customers can reply anytime they want, no matter in which status.

Thanks!

Jack Brickey

True but you don't, I think, want an issue to transition to waiting for support anytime a customer comments. Generally the workflow is like this...

issue is in Waiting for support and agent needs more info from customer
agent responds to customer and causes a transition to Waiting for customer
customer comments back which results (thru Automation) in a transition back to Waiting for support

So, for example, let's say the status is something like Pending and a customer comments on the issue "Hey what is the latest". In this case you wouldn't want it to go back to Waiting for support.

With that said, what are your requirements? Have you checked your Automations? If so what did you find?

Gui Ávila

@Jack Brickey Thanks a lot.

I thought that did not work with automations, that was something related to post functions or similar. I might be wrong, but when I created the project already worked the way you described, and there was no automation set.

But if the way to go is via automations, all right. I will do that.

Thanks!

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