Service Desk Satisfaction ratings (CSAT) should be tracked historically

 Problem Definition

Since Jira Service Desk CSAT (customer satisfaction) system currently permits users to re-submit their satisfaction star ratings multiple times (see also JSDCLOUD-3839 ), Jira should be able to track these changes from a historical perspective. Currently this is not possible. Since the data is being stored on a custom field, as soon as the customer changes their star rating, that value overwrites the previous data for that interaction.
While the issue history in Jira does indicate the date/time of a satisfaction rating was provided, it does not track what that rating was.

In turn these original ratings are lost.

Suggested Solution

Track the historical rating values in some manner. Either in the issue history, or when viewing the changelog of the issue via the API, this information would be useful to be able to store and retrieve.

Why this is important

It is possible for a customer to incorrectly update the wrong request, or worse update all their previous requests and change these values. This provides a very skewed CSAT values if done, and does not accurately reflect the original CSAT ratings given initial provided

Workaround

None