Empezar con integraciones de herramientas para desarrolladores
¿Por qué se debe vincular el código con las incidencias de Jira?
Caso práctico 1: Visibilidad de tu canalización de desarrollo en 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.
Caso práctico 2: Automatizar Jira a través de los cambios de código
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.
Caso práctico 3: Buscar en Jira mediante la información sobre el desarrollo
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
Cómo vincular código con las incidencias de 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.