Wouldn't it be good to have all issues and discussions related to a given Pull Request (PR) gathered and sorted in one convenient feed-like summary?
Well, it's here!
We're very happy to introduce our new very cool feature that does just that. We call it 'Auto-linking'. It allows issues to be related to pull requests and have Keypup group these items automatically in your priority inbox for better visibility. And the best of it? You don't need to do anything extra as it integrates natively with existing auto-linking features of GitHub or GitLab.
So how does it work?
Let's assume an issue is open and scheduled for this week.
This issue automatically appears in your Keypup priority inbox as usual.
Now you do some work and open a pull request on GitHub or another code repo you use. You now see two items in your priority inbox... Not so great as these two items are essentially the same.
Well, let's just change the description on our first pull request by adding the keyword "Closes <my issue number>" like so (In our example, 51 closes 54 indeed):
Your Keypup priority inbox picks up the relationship between the two items and combines them as a the one discussion!
The auto-linking feature automatically creates a unified conversation feed across all items. This makes it way easier to ensure that you haven't missed any update on a related item. Note that you can still access each individual item related discussion separately as well:
This works with any number of issues and you get a nice summary by clicking on the inbox item.
For all your items you can see at a glance a summary of all issues and PRs an items solves at once. Convenient hey?
Review and Merge Board
The same, just when you're about to conclude. Talk about a wing person!
Finally the due date of your pull request gets automatically updated based on the due dates of the related issues.
This due date discovery feature is particularly important when assigning your pull request for review. Based on due dates Keypup will automatically adjust the priority of the item in the priority inbox of the reviewer you have assigned - there is no need to manually assign a milestone to your pull request anymore. Win! :)
By the way, when you use Keypup to assist you with the project management your activities, this is a considerable little helper too!
Want to know about the nuts and bolts? Right here...
The auto-linking feature works by analysing the title and description of your pull requests, looking up references to issues across all the systems you have connected to Keypup.
Here are examples of keywords you can use in your pull request descriptions to auto-link items:
- Closes #54 => Links the pull request to issue 54 in the same project
- Fixes #54 => same (different keyword)
- Resolves #54 => same (different keyword)
- Closes myorg/other-repo#54 => Links the pull request to issue 54 in a different project
- Closes https://github.com/myorg/other-repo#54 => Links the pull request to issue via url
On top of GitHub/GitLab native rules, Keypup also looks for issue keys in pull request titles:
- #54 My PR title => Links the pull request to issue 54 in the same project
- [myorg/other-repo#54] My PR title => Links the pull request to issue 54 in a different project
- [#54][#56] My PR title => Links the pull request to issue 54 and 56 in a different project
Auto-linking works across systems. So if you have connected GitHub, GitLab and JIRA you can reference issues across them:
- Closes my-gitlab-org/repo#23 => Links a GitHub or GitLab pull request to a GitLab issue
- Closes JIR-123 => Links a GitHub or GitLab pull request to a JIRA issue
- Closes https://myorg.atlassian.net/browse/JIR-123 => Links a GitHub or GitLab pull request to a JIRA issue via url
- [JIR-123] My PR title => Links a GitHub or GitLab pull request to a JIRA issue by inserting the JIRA key in the pull request title.