Can I limit when an issue is considered "updated"?

[Robert Ortega]

Is there a way to only consider an issue "updated" when its a comment from the requestor or the assignee?  We're separately monitoring when items are updated and any change to the issue is considered an update so it's understating the problem.  Is this possible?

[Matt Doar]

Tricky. I would leave the Updated system field alone and create a Scripted Field (assuming Data Center and the ScriptRunner app). The field can look at the History of an issue and determine a date value based on when there was last a change to the issue that you are interested in. 

Not sure about Cloud though

[Nic Brough -Adaptavist-]

Yes, very tricky.  On DC/server, there are some tricks you can play to lie about "data on this issue changed", but I have not found a way to lie about it on a Cloud system.  

If you change data on a Cloud issue, the change is recorded.  It is what issue trackers do.  (The exception for Jira is ranking, that happens too much for it to be worth tracking, and as @Matt Doar says, do you really care about it?)