How does Keypup help developers daily?

Let us show you how Keypup works through a real-life use case that might look familiar to you
Jenny, she is a tech lead
Bob, he is a frontend developer working with Jenny
...they already use...
Jira and Slack are not required to use Keypup. GitHub, GitLab or Bitbucket alone is sufficient.
...and working with Keypup looks like

It's sprint time!

Jenny logs into JIRA and assigns a couple of issues to Bob for this week.
Layer 1
All issues from his different apps in one place

Bob is ready to work!

Bob sees two issues in his Keypup priority Inbox with all the details he needs: description, comments, due date, labels etc.
Layer 1

A pull request is opened

Bob opens a Pull Request on GitHub with his items and links both JIRA issues using auto-linking keywords.
Layer 1
PR and issue discussions gathered in a single feed

Issues get grouped automatically

Thanks to auto-linking Bob only needs to follow a single item in his Keypup Priority Inbox instead of tracking his pull request and the two issues individually in his other tools.
Priority Inbox- grouped issues
Layer 1
Automated reminder of daily priorities

Next morning at 9am

Bob receives a digest via Slack with a reminder on his current priorities.
Go for it Bob!
Layer 1

Time for review!

Bob is finished with his pull request. He assigns it to Jenny for review. The item is automatically moved from his prioritized list to the Pending Peer tab.

This keeps Bob's prioritized list actionable and clean!
Pending peer tab
Layer 1
Automated assignment for PR actions

Jenny's turn to review

Because Bob assigned Jenny on his pull request, it automatically appears in Jenny's Priority Inbox with an action set to Review.
Priority inbox - review
Layer 1
Efficient collaboration between team members

Changes required on Bob's pull request

Jenny has made her review and requested Bob to change a few things. The pull request comes back to Bob's Priority Inbox with action Address review changes.
Priority Inbox - review changes
Layer 1
Centralized view of all PR status and progress

Meanwhile Jenny keeps an eye on all pull requests

The Review & Merge board allows Jenny to quickly review the status of pull requests across the team. No more stale PRs due to information spamming!
Review and merge pull requests
Layer 1
No more useless back and forth during reviews

Bob assigns Jenny for re-review...but wait..what?

Looks like the build is failing now. Despite having assigned Jenny for review the item remains in Bob's Priority Inbox with action Fix build.
Layer 1
Quick merge in one click

Ready to merge!

After Bob fixes his build, Jenny approves the pull request.

Because Keypup has automatically detected that Jenny was the project maintainer, the PR is moved to Jenny's Priority Inbox with action Merge.
Layer 1

Want to simplify the way you develop?

Get started