The following endpoint:

(Post) Bulk fetch changelog

Has two filter methods:

• issueIdsOrKeys
• fieldIds

The first one is required; it enables issue-level filtering

The second one is optional; it allows a changelog object filter level

Multiple changelog type entries don't include fieldid as one of the object keys. One example (but there are various scenarios) is for a key change:

{
   "field": "Key",                  
   "fieldtype": "jira",
   "fromString": "XPTO-1",
   "toString": "XYZ-3"
}

Cases where fieldId is not present are only accessible without the fieldId parameter, so it's necessary to request the entire changelog of an issue to access a specific log.

Since not all logs have fieldId, and currently, the fieldId is the only filter available on log level, this filter doesn't comprehend all logs. To avoid getting all the logs, it would be beneficial to have another way to filter on a log level: to search for a key on the log object shared by all log entry types.

This would be done by having two filters at the log level, where fieldId and fields can be used. In this suggested search, fieldIds should have precedence over fields. If both fieldId and fields are informed in the query, the fields will be used as a secondary filter, so if fieldID isn't available, it will use fields instead.