Ok, the short answer is "no", because a field is simply a field. It holds the current value, and doesn't need to do anything else.
The full history of change on any field is part of the issue history. If a user is viewing an issue, that is there in the history tab, but of course, it's the entire history. You could construct a scripted field that would read the history for your field and pull that out, and then show it under or alongside your field, but you will need coding to do that.
I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...
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