Getting 'CONFIG CHANGED' status during Jira automation

[Aram]

We are using Jira cloud with hosted Bitbucket server.
These 2 servers connected to each other with application link. It is possible to create branch, PR and monitor results from Jira. So, seems they are connected each other successfully.

I need to do some automation when:
 1. branch is created move issue to 'inprogress'
 2. PR is created move issue to 'code review'
 3. PR merged move issue to 'Resolved'

I have created all of them but it is not working. So I have checked Audit Log and I saw that status is 'CONFIG CHANGED'.

[SPHIOR]

"CONFIG CHANGED" in the audit log usually just means Jira detected a configuration change happened around that time (workflow, automation rule edit, etc.) — it's not itself an error state for your automation, more of a marker that something in the setup was touched.

For the actual automation not firing, I'd check a few things separately from the audit log:
1. Go to the rule's own Audit log (inside the automation rule itself, not the global Jira audit log) — it'll show whether the rule triggered at all, and if it errored out or just didn't match your condition.
2. Double check the trigger scope — "branch created" and "PR merged" triggers usually need the dev panel/smart commits properly linking the issue key in the branch/PR name. If Bitbucket isn't passing the issue key correctly, the rule won't fire even though the integration "looks" connected.
3. Check whether the automation rule's actor has permission to transition the issue in that specific workflow — a common silent failure is the rule running but the transition being blocked by workflow conditions.

Worth checking the rule-level audit log first since that'll tell you definitively whether it's a trigger problem or a permission/workflow problem.