Best practice: How to store issue related values (e.g. number of transitions)

[Chris Lange]

Currently we're using script runner to update some custom fields (configured as text (read only)) to track the number of transitions. But unfortunately we don't want to distract the users on the screen with these values. It's more an internal thing which should be accessible only to a few people.

Currently I don't see any other approach than having these custom fields on the screens. Otherwise we are unable to edit the fields during transitions.

I guess we are not the first ones running into to issue so my question is: is there a better way to store issue related values internally? 

[Nic Brough -Adaptavist-]

Are you Cloud or Server?

I ask because Server scripts should let you set fields that are not on screen (and do scripted fields which also don't have to appear on screen, and could do the calculation based on the history instead of updates)