Native Git/PR integration

Native Git and pull request integration means a tool talks to the place where the code lives, without a separate connector. A task can be linked to a branch, a commit or a pull request, and its status can change by itself when the pull request is opened or merged. In practice, a developer writes the task number in a branch name, and the task moves to done once the change is merged. Linear and Emergent are listed as having it.

Teams that track work in one place and write code in another often end up with boards that are out of date. Linking the two removes manual status updates and shows the business what has actually shipped. It matters for any team that works with developers, including agencies you hire. It is not needed if no software is being built, or if a single person manages both the tasks and the code.

• Ask which Git hosting services are supported, such as GitHub or GitLab, and whether both cloud and self-managed versions work.
• Test whether a merged pull request changes the task status without anyone touching the board.
• Check what the integration can read, and whether it needs access to every repository or only chosen ones.
• Ask whether the link works in both directions, so a task can show its pull request and the pull request can show its task.