How can I modify an issue via API without creating history/log content?

[Matthew Karam]

We use JIRA to record incidence rates of specific infrastructure logs. 

While the ticket is open we want to maintain a count of the number of times the log has occurred, but this could be in the hundreds of thousands.

The problem we have is that if our listener increments the count in JIRA then each update creates a sizable log entry like "Count changed from 500 to 501" repeated many times.

This is not useful log data and it creates immediate stability problems in JIRA when viewing the ticket. It also creates excess data.

Is there any way to modify issues via the API without generating history or log content? 

[Nic Brough -Adaptavist- · Accepted solution]

Not over REST, it respects all the built-in rules.  Your best best is to write a new field that explicitly disables its own logging.

[Matthew Karam]

Are you suggesting a plugin which modifies the DB directly, rather than via the REST API? Or is there some way to configure a field so that it doesn't log its own changes?

[Nic Brough -Adaptavist-]

Not quite, I'm suggesting an add-on that provides an issue field, but one that deliberatley does not implement the "write to history on change" function. There's no way to configure this, it's all in the code