I have the Satisfaction Settings turned on in the Jira project I wish to enable the functionality in.
I'm currently having an issue with the form not being shown to the customer when the tickets resolution is set.
Everything that I have configured matches what's mentioned on this page.
My Resolved status is Done rather that Resolved though, could that be causing the problem?
This survey is not sent out based on the issue's status, but rather when the issue gains a value in the resolution field.
How is the resolution being set for issues in this workflow? Is the resolution selected via a transition screen? OR is the resolution set via a post-function in the workflow?
You can use either of these methods to set a resolution for an issue depending on your workflow, but your workflow should never be set to use both methods to set the resolution value on an issue. I have seen setups were admins set the resolution value by both methods and doing so tends to break this functionality of the customer surveys from being sent to the customer.
It is strange to see that your workflow is also setting the assignee to the value of the reporter. That part should not usually be possible in a service desk project since only Agents are able to be set at the assignee of issues in a service desk project. That is not common to see, so perhaps that post-function is a factor here.
If that is not the problem here, then I would want to understand if perhaps these issues are set with a different value for the resolution field before this transition is executed. In most cases, issues in Jira should not have a resolution value at all until the issue is ready to be completed. However I have seen instances where a project admin will set the resolution field to be required in the field configuration. When this happens, it requires that all issues have a resolution value, even when they are created. This can circumvent the way Service Desk is intending to trigger actions like the sending of satisfaction surveys.
Thanks for the response @Andy Heinzer.
I've removed the assignee post function as mentioned and still no luck I'm afraid.
After investigating your comments on the resolution status being set beforehand I can't find any evidence of this in the workflow.
Is there anything else I can provide in order to resolve this?
Thanks for letting us know the solution here. Did you have to set the resolution post function before the reindex post function? I could see a scenario where having the resolution set after the issue is reindexed might not trigger other features like this satisfaction survey.
Hello Community 👋, I'm a product manager at Atlassian, looking at improving change management capabilities across our products. In particular, we're looking at bridging the gap between Dev & ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events