The Priority inbox uses pre-built logic to evaluate the priority of items related to you. The default logic we provide may not always fit your development workflow or you might want to track/untrack specific items based on a number of conditions to improve the overall accuracy of your inbox.

We've got you covered with Prioritization Rules.

Prioritization rules are matching filters allowing you to override the default priority classification provided by Keypup. They can be used to improve the overall accuracy of priorities in your inbox as well as to create reminders on items that must be actioned.

Prioritization rules can be personal or team-wide.

Creating prioritization rules

To get started with prioritization rules head to User Profile > Prioritization Rules.

Examples of prioritization rules

Add a prioritization rule by clicking on New rule.

When creating a rule the following details should be specified:

  • Name: just a way to keep your rules organized

  • Rule Scope [admin only]: Whether to apply this rule to yourself or to the whole team.

  • Precedence: items match rules on a first-match basis. You should put more restrictive rules at the top and less restrictive rules at the bottom. For team-wide rules we recommend setting an order of precedence above 1000 so as to allow individual team members to override them.

  • Hint: a short sentence that will appear on items to remind you why they have been assigned this priority.

  • Priority: the priority to assign to items matching this rule.

  • Matching rules: a series of AND/OR conditions on fields used to match pull requests and issues.

Hit Save and your prioritization rule will be applied immediately. You can head to your Priority Inbox to see the results of your rule(s).

Personal rules you create are only applied to your own account - so there is no risk to impact team members when you start playing with rules. If you wish to apply the rule to all team members, change the Rule Scope to Team.

Always consider exit conditions

Remember that items matching your rules will stay in your inbox until their attributes change and do not match the rule anymore. 

Therefore you should always think about practical "exit conditions" for each rule, otherwise you'll end up with many non-actionable items filling your inbox.

An exit condition means "How will items disappear from my priority inbox?".  Exit conditions can typically be based on:

  • State: my item should appear in my inbox until it's merged/closed.

  • Time range: my item should appear in my inbox only if it was created/updated/merged within the last 24 hours.

E.g. Tracking un-triaged items
Let's say you want to prioritize issues with label triage-required to ensure you check each of them and assign labels/assignees.

A basic filter would look like:
if label includes triage-required then assign priority IMPORTANT

This might work alright for you depending on the number of issues you have to triage. 

But if you have a high number of issues you might prefer to only prioritize new un-triaged items for one day. This would allow you to get a heads up every day on new items, address the important ones and leave the non-addressed ones for the next monthly review.

Your filter might become something like:
if label includes triage-required AND created_at > 24 hours ago AND created_at < 0 hours ago then assign priority IMPORTANT

The filter above would give you a nice reminder on new un-triaged items without filling up your inbox growingly if you don't take the time to triage items.

Did this answer your question?