Pulse naming conventions - Shortcut
Pulse naming conventions - Shortcut. Jira Naming conventions LinearB matches Git work to Shortcut issues. In order to match branches to issues, the LinearB matching algorithm needs branches and pull…
Pulse naming conventions - Shortcut
LinearB matches Git work to Shortcut issues. In order to match branches to issues, the LinearB matching algorithm needs branches and pull requests names to align with the issue code provided to each issue (and sub-task) by Shortcut when the ticket is created. LinearB searches the ticket code within the name of the branch/PR as well as its commits. Each branch/PR that includes the issue/sub-task code in its name will be matched to the relevant issue and will be included in the Pulse view.
For example:
If the ticket name in Shortcut is: "Infrastructure story" and the ticket code is: 4584 the branch name should include "ch4584" (not case sensitive) in its name:
- ch4584-Add-repository-bakcfill-status
- ch4584-Add-repository-status-enrichment
In this example, both branches (from different repositories) will be matched with the issue above.
How did we do?
Pulse naming conventions - Jira
Understanding the Pulse View