Change to the way Satisfaction Surveys work?

[Nathan Allen]

I believe a change was made to the way Satisfaction Surveys work, and I'm hoping someone can confirm.

Previously, you would select a star rating and then enter an optional comment, then click submit. At that point, the satisfaction score would be updated and the comment would be saved to an issue property: {{issue.properties.service-request-feedback-comment.comment}}.

Now, when you click the star it appears to update the score immediately and then if you choose to add a comment, it saves it when you click "Add a comment".



I was triggering an automation on the Satisfaction score changing, then retrieving the comment and sending the comment out to managers of the teams. But now, that property is empty since the score updates many seconds before the comment - depending on how long they take to type it.

This wouldn't be a problem if the comment was stored in a field instead of a property, but I don't think there is a way to trigger an automation based on a property changing.

Would love to know if this was an intentional change or if it's a bug that will be fixed.

[Andy Heinzer]

Hi @Nathan Allen 

I created a support request based on your post here.  You can find this over in https://support.atlassian.com/requests/PCS-264338/

Someone from our JSM support team can review this and will reply.

Regards,

Andy

[Nathan Allen]

Thanks Andy.

[Christopher Maxwell]

Hi @Nathan Allen great details and information. It's not something I can help with but I'm flagging this to Atlassian's attention to see if someone on staff is able to answer your question.

[Nathan Allen]

Thanks!