Bulk editing mapped fields in an Aha! list report doesn’t send the changed values to already-linked Jira or Azure DevOps records in the customer’s setup.
Teams must take extra steps to sync the changes, leaving downstream records out of date in the meantime.
When a list report bulk edit changes a mapped field, send the new value through each record’s existing Jira or Azure DevOps integration.
Honor each integration’s automatic-send or approval settings without requiring a separate Send to action or a release-wide resync.