Code

Overview

Constructor has a powerful integration with GitHub to automatically link pull requests with tickets.
When a pull request is linked to a ticket, you'll get several benefits to streamline your team's collaboration:
  • Real-time PR status: Open PRs are displayed right on the board on the ticket's card, including their title, live build status, deploy preview and other CI/CD links, review requests, merge conflict status, and more, making it easy for you and your team to stay on top of development activity and jump in when a PR needs attention.
  • Easier, more timely code reviews: Constructor helps teams stay on top of code reviews by displaying pending reviews right on the board on the ticket's card, as well as in the reviewer's "My work" view. Also, Constructor posts a comment on the PR in GitHub with the ticket's details. That makes it easier for code reviewers to know what a PR is for without having to navigate back to Constructor.
  • Knowledge retention: Merged PRs are permanently retained in the linked ticket's details. Not sure how a ticket was implemented? Open the ticket in Constructor and the PRs are all right there. Not sure why some old code was written? Open the PR in GitHub and follow the link left by Constructor to get back to the ticket.
Learn more about the GitHub integration:

Step-by-step

Linking a pull request to a ticket

To link a pull request with a ticket, just ensure the pull request's head branch name contains the ticket ID in a recognized format. When you open the pull request, Constructor will automatically link it to the ticket.
Constructor generates a suggested branch name for each ticket using the ticket's ID and title. You can grab this suggested branch name while on the ticket's page or while on the board:
  • While on the ticket's page: Scroll down to the Code section and click the copy button next to the suggested branch name.
  • While on the board: Hover over the ticket's card and click the ellipsis menu, then choose Copy branch name.
The suggested branch name is just that, a suggestion. You can also use your own branch name as long as it contains the ticket's ID in a recognizable way. For example, for ticket ID #123, the branch name could use these patterns:
  • 123-foo-bar
  • 123_foo_bar
  • baz/123-foo-bar
Need a different branch name pattern? Contact us.
To view the pull requests associated with a ticket, visit the ticket's page and scroll down to the Code section. You'll see both open and merged pull requests linked to the ticket. Click any pull request to open it in GitHub.
In addition, when you view a board, open pull requests are shown on the associated ticket's card, giving you and your team better visibility and quicker access.
When Constructor links a pull request to a ticket, it posts a comment on the pull request in GitHub with the ticket's title, description, and other details, along with a link back to the ticket in Constructor. This makes it easy for code reviewers to know the context of the pull request without having to open the ticket, and makes it easy for anyone to navigate to the ticket if they need to.