Which Jira Software issue key reference approaches are currently supported by Develop with AWS (Jira)?

Develop with AWS (Jira) integrates your AWS DevOps toolchain with the Atlassian Open DevOps experiences in Jira – Jira Software supports 4 core approaches to https://support.atlassian.com/jira-software-cloud/docs/reference-issues-in-your-development-work/:

Develop with AWS works event based, so just as with your Git integration for Jira, you need to push something to the connected repository to trigger a deployment/build (or do so manually) so that the AWS service event can be ingested to Jira Software (events usually surface in under one minute).

	CodePipeline	Notes
Branch name	IN THE WORKS	The CodePipeline events readily include the branch name so we can provide this capability soon.
Commit message …
… of last pushed commit	SUPPORTED
… of all pushed commits	UNSUPPORTED	The CodePipeline events only include the last commit ID, so if a push contains multiple commits, we lack access to the resp. commit data – we are investigating how to eventually work around this via a CodeBuild action that uses a full clone to extract and forward this data.
Pull request title …
… before merge	UNSUPPORTED	We do not have access to pull request data from the various upstream Git providers, so this seems blocked for now.
… after merge	CONDITIONAL	This works if your Git tooling references the issue key … … either in the PR title and in the subsequent merge commit message (default workflow in e.g. GitHub, where the title is used in the commit message, while the PR ‘description’ aka first comment is ignored) … or alternatively in the PR description and in the subsequent merge commit message (default workflow in e.g. Bitbucket, where the description is used in the commit message, while the PR title is ignored)