Assignment history is extremely important to my customer. For some obvious transparency and traceability reasons this is something they want to be able to track. In the past, I've created various "position/title" user picker fields, but that doesn't quite fit the desired functionality.
Then I saw this in the Adaptavist Library: Show Assignee History on Issue Details Page https://library.adaptavist.com/entity/show-assignee-history-on-issue-details-page
I wish I had a screenshot to show what the ScriptRunner script fragment produces, but this is what it resembles (Credit: PowerPoint Magic):

This script is great! My customer LOVES the simplistic solution.
The down-side to having the script fragment (for my customer) is the following:
- It cannot back-date... all precluding history changes are not captured so for pre-existing projects, the assignee history is incomplete.
- I assume this has to do with the fragment acting like a counter for a specific event.
- This leads me to concerns about how this information is retained, and what would happen if the system crashed, how is the data stored, and how taxing is it on the system memory?
- There is no simple way to query against the data as a script-fragment.
- At least not for the average user, I'm sure you can with JQL functions.
- There is no way to aggregate or export the values.
- Script-fragments don't export, not even when exporting to print.
It's got me wanting to aggregate this in a scripted field...
Problem is...
- First, I'm not sure what the most efficient and sustainable way to do this is, AND
- Second, I'm not sure how to modify the script to have it append the assignee history in a scripted field.
- I think it might be accomplished with a listener and scripted-field combination.
- I'm also concerned about having multiple values, and how to keep them separate, and meet the customer needs (let's be honest, "wants") listed above.
I'm open to suggestions, but I am limited within my strict environment. Buying a new add-on(s) is not an option till next FY quarter (if then).
---
I have a feeling, someone in the community has this same ask/question, and I think it could be accomplished in several ways. I'm about to go down this rabbit-hole, but if anyone has suggestions or has already come up with this solution, I'd be extremely grateful!