You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
I have an automation rule that cancels a ticket after 48 hours of no update if in Waiting for Customer, but it still sends the survey.
Is there a status or resolution that does not trigger the survey?
By default - CSAT is triggered when issue is resolved in JSM. The definition of issue is resolved is controlled by the Resolution field value is populated. I am sure you are already aware of that aspect of JSM.
So the only way for you to avoid the CSAT from being send out is that if an issue's transition into a WF status that doesn't populate the Resolution value. Thus the system is not treating your cancelled issue via your automation as an resolved issue.
CSAT is either enabled or disabled at the project level, so you cannot truly control to prevent CSAT from being triggered. There is no resolution or status that can stop it for issues.
Lastly, the drawback of setting up a WF status that you can use for cancelled issue while leaving the Resolution field value as NULL is that the issue will not be dropped off from your queue. It is because the system still consider the issue as unresolved.
Hope this helps and sorry no other solution for controlling CSAT process in JSM as far as I know of it.
Best, Joseph Chung Yin
Jira/JSM Functional Lead, Global Technology Applications Team
Is there a way to disable the customer notification for a particular transition?
i.e. if I make a new status of Auto Resolve. Is there some way in the transition step I can disable the emails to the customer?
If I set an issue to resolved but do not populate Resolution the survey is still sent.
Unfortunately, it is not possible. It is odd that when you stated an issue moved to resolved but the resolution field is NULL still triggers the CSAT.
It is my understanding/experience that the Resolution field must be NULL, so the issue is not treated as Resolved.
Currently there is an enhancement request - https://jira.atlassian.com/browse/JSDCLOUD-5691 on providing some functionality on CSAT processing (i.e. notification). You should add yourself as a watcher of it.
My next recommendation is for you to contact Atlassian Support (https://support.atlassian.com) for further assistance.
Maybe I am setting Resolution to null incorrectly.
In a manual automation I am transitioning to Resolved
the edit the issue with this in the Additional fields
Should I approach it in a different way
You never set Resolution field value via automation. Setting of the Resolution field value is controlled in your WF's via the transition post function by default.
So you should modify your WF's transition to not set the resolution field value. If you take a look at your existing WF's transition to "Done"/"Closed"/"Resolved" statuses, you will see in the post-function that it is setting the Resolution field value.
In your new WF status, you can even add the post function to set Resolution field to "None" - Essentially it is ensuring that the field is empty.
Hope this helps.
Tried that. I have a new Status. Post Function that sets Resolution to None (clears the field). CSAT still sends.
Will hit up support.