You are viewing an old version of this content. View the current version.
Compare with Current
View Version History
« Previous
Version 6
Next »
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/:
| 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 | WORKAROUND | 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.
Depending on your workflows, you might be able to leverage the following workarounds:
|
Pull request title (and description) … | | |
… 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/squash commit message (e.g. the default GitHub merge workflow, where the title is used in the commit message, while the PR description is ignored unless changed in repository settings – see default GitHub squash workflow for an alternative) … or alternatively in the PR description and in the subsequent merge/squash commit message (e.g. default Bitbucket merge workflow, where the description is used in the commit message, while the PR title is ignored)
|