The Jenkins console output shows that the commit message has the Jira issue key:

{{ > git checkout -f 6db08a0ec4b8fc9395b696cba7419bc6cf4ce5cf # timeout=10 Commit message: "Merged in hotfix/TB-5521 (pull request #1398)" }}
{{ > git rev-list --no-walk 3b1a9984adfb06956a8626b5d3c2b54a639e9dc7 # timeout=10}}

but later no deployment info is sent:

[Pipeline] jiraSendDeploymentInfo jiraSendDeploymentInfo(foo.atlassian.net): SKIPPED_ISSUE_KEYS_NOT_FOUND_AND_SERVICE_IDS_ARE_EMPTY: No issue keys found in the change log and service ids were not provided. Not sending deployment information to Jira: foo.atlassian.net.

The PR had a branch name of `hotfix/TB-5521` but the PR name, single commit's message and PR body do not contain the Jira issue key. The Jenkins job is building a branch named `aws-qa` which this PR has been merged into.{}

If it helps to debug, the Jenkins "Changes" tab contains a link to the commit that is bundled in the merge commit. The Changes tab doesn't reference the merge commit.

Changes

Summary

1. -Cascade save and delete from AppDomain to Config