Query repository and development data and save reports with the Keypup Data Explorer

Get better insights on development activities data with the Data Explorer.

Did you ever feel the need to have access to advanced querying in your development systems? Can't stop jumping across browsing tabs to get an overview of your issues and pull requests state from your repositories? Fed up with having to perform API calls left, right and center to get some sort of visibility? How could you possibly have a clear view of ALL your development items in one click ?

Well, your data search doesn't have to be a nightmare anymore. And that is a pretty bold statement. So let's back it up with facts.

Maybe a little query editor would do no harm, so we just created one. If you feel like us then the new Keypup data explorer is made for you.

The data explorer allows you to easily query pull request and issue data and save these queries as reports. Reports can also be pinned as tabs on your priority inbox for easy access.

No API calls. All queries and reports in the one place. Yep - that simple. And really performing - the reports you will get can be customized at will and have many conditions. Oh, and they're dynamic, so once created, you can just follow up on them to see your progress.

Building queries

Alright, let's see how this toy works. Let's head to Report > Data explorer. From there you can do a few things to build your report.

The query editor is where you can implement all the filters you need to build your query. The query editor is composed of 5 important sections:

DE- Query Editor

1. Query explainer

The query explainers provides a summary of the query that will be run on our servers. The explainer aims at being a compact and visually friendly representation of the filter created in section 3.

2. View options

This section allows you to configure different flavours for your report. There is only one option available at the moment but more will be proposed in the future.

  • Unnest related issues: Issues resolved by pull requests via auto-linking keywords will be nested under their respective pull request by default and will not appear as individual items in the results. If you wish to list all issues no matter whether they are resolved by pull requests or not then tick this box.

3. Query editor

This section is the most important one. It allows you to create comprehensive filters using AND/OR conditions on item fields (e.g. created_at or author).

The editor provides common matchers for each field type (equal, different, greater/less than etc.).

The editor also provides some more dynamic matchers on some specific fields:

  • Timestamp fields (created_at, due_on, updated_at etc.) have before/after X hours ago and before/after X hours from now matchers. This makes it more convenient when you want your reports to be dynamic and get updated over time.
  • user fields (author, reviewers etc.) allow you to select yourself (is me and include me in array fields). These filtering helpers are more robust than hardcoding system-specific usernames using = (equal) matchers. By using is me or include me filters, Keypup does the hard work of reconciling who you are in each system.

4. Report results

This section displays all the items - along with their current priority - matching the filter you configured in the query editor. The display is similar to what you can see in your priority inbox.

DE- Report results

5. Report save options

Once your query is nice and beautiful you can save your report for later use.

The actions presented are the following:

  • New: start a new report from scratch
  • Save: save the current report. The next screen will propose you to give a name and a description to your report.
  • Save as new: save the current report as a new one. This is convenient when you want to build a new report based on another one.
DE- Save report

Once saved your report will appear in the Saved reports tab:

DE - Saved reports list

Adding tabs to the Priority Inbox

Reports created via the Data Explorer can be pinned as a tab on your Priority Inbox. This is an easy way to customize the Priority Inbox and quickly access the items that are mission-critical to your development.

There are two ways to do it.

From the Data Explorer

Simply save your report then tick the Pin report to priority inbox tab option. Upon ticking this box a field appears allowing you to configure the order of appearance of the tab.

Note that custom tabs will always appear after the default tabs (Prioritized, Pending Peer, Coming up and Recently Closed).

From the Priority Inbox

You can add a custom tab by clicking on the + (plus) icon in the list of tabs.

DE - Pin to Priority Inbox

This will redirect you to the Data Explorer and set the report to be pinned to your Priority Inbox by default upon saving it.


Let us know what you think of this feature !

#Update: Keypup now provides auto-discovery of JIRA custom fields. Upon connecting your JIRA instance, Keypup automatically fetches and makes available filtering all JIRA fields with supported data types. Read the article to know more about it!

Don't have an account yet and ready to try? Sign up here for free. (yes, it's totally free)

You may also like reading: