Débuter avec l'intégration aux outils de développement
Pourquoi associer du code aux tickets Jira ?
Cas d'usage n° 1 : Visibilité au sein de votre pipeline de développement depuis Jira
The development panel on the Jira issue screen summarizes key development information such as branches, commits and PRs for each issue. This improves cross-collaboration between teams like engineering, QA and operations. Learn more about development information in Jira.
Cas d'usage n° 2 : Automatisez Jira via des changements de code
Instead of manually updating the status of an issue after creating branches or merging pull requests you can configure triggers in your workflow to automatically transition issues when certain events occur in your development tools. Learn more about automation with Git information.
Cas d'usage n° 3 : Faites une recherche dans Jira en utilisant les informations de développement
Get deeper insight into your complete software pipeline from within Jira Software. You can create powerful views across your full software pipeline from backlog to production. Query Jira data based on Git, build or deployment information. Learn more about the Jira Querying Language (JQL).
deploymentEnvironmentType ~ production AND development[pullrequests].open >= 1
Comment associer du code aux tickets Jira ?
When development tools are integrated with Jira Software, you simply add the Jira issue key in your development tool to link information. Below is a handy table of how to link Jira issues from your development tool:
Branches are linked if the issue key is included in the branch name.
Commits are linked if the issue key is included in the commit message.
PROD-1274 Fix eslint error and update tests
Pull requests are linked if the issue key is included in the pull request's title or in the source branch name.