In Jira Cloud, any change to an issue (via UI, REST API, or Marketplace app) updates the system-managed Updated field. This also applies to automated or system-driven updates that do not represent meaningful user activity on the ticket.

This behavior can negatively affect some users who do:

• Reporting based on "Last updated"

• SLA calculations that use "time since last update"

• Audit or operational timelines that need to distinguish real user activity from background/system updates

Current behavior

• Any issue update (including automated updates by Marketplace apps or integrations) causes the Updated timestamp to be set to the current date/time.

• There is no supported way to:

 mark an update as "system/administrative", or

perform a "silent" update that does not modify the Updated field

Requested behavior / Enhancement

Introduce a Jira Cloud platform capability that allows:

• Apps or API calls to update issue data without changing the Updated timestamp, when the change is purely administrative or system-driven.