GitHub Projects is now available!

This update brings powerful new capabilities to Keypup, headlined by our integration with GitHub Projects and a suite of versatile reporting fields. Seamlessly track your GitHub Projects data and gain unprecedented control over your reporting!
GitHub Projects Integration: Gain Project-Level Visibility for your Repositories
Now you can properly track issues and pull requests managed through GitHub Projects, gaining a comprehensive view of your project's progress directly within Keypup. Our integration goes beyond simple issue tracking, allowing you to:
- Track Multiple Projects: An issue or Pull Request can belong to multiple GitHub Projects, and Keypup captures this, allowing you to analyze progress across different project management layers.
- Leverage Project-Specific Fields: Each GitHub Project's status, iteration (mapped as Sprint in Keypup), and custom fields are imported, enriching your reporting with project-level context.
- Avoid Data Duplication with Filtering: To prevent confusion arising from duplicated issues across different GitHub Projects, leverage Project-level or App-level filtering to ensure your reporting focuses on the right project.
- Access Key Project Data: The integration captures key attributes like Status (mapped to Workflow Status), Iteration (mapped to Sprint attributes), Project Name, and Project Source, enabling richer reporting and analysis.
- Filter by Sprint Attributes: Leverage Sprint attributes (Sprint Name, Sprint End Date, Sprint Start Date, etc.) to filter issues and pull requests based on project iterations.
- Complement Existing Integrations: Our GitHub Projects integration supplements your existing GitHub integration, providing project-level insights on top of repository data.
To know more about it, read our dedicated article about GitHub Projects.
New Reporting Fields: Source Workflow Status & Cross-entity fields
Take your reporting to the next level with our newly added reporting fields. Filter across resolved issues &Ā PRs, generate historical "at date" charts on activity events and calculate more granular metrics like Review Cycle Times!
- All Datasets > Project Account: exposes the name of the parent organization/workspace.
- Activity Events > Source Workflow Status: capture the source status on transition events. See our new insight Historical in status at date for an example of usage.
- Issues/PRs > Project Source: used to capture the underlying repositories with GitHub Projects.
- Issues/PRs > Resolved Issue Projects: provide the ability to filter PRs based on resolved issue projects.
- Issues/PRs > Resolving PR Projects: provide the ability to filter issues based on resolving PR projects.
- Reviews > Requested at: capture the moment the review was requested for each review.
Other improvements and bug fixes
- Improvement: Drilldown/Filters - allow custom dimensions (using formulas) to be used in filters and drilldown. The drilldown auto-configurator now takes into account custom dimensions.
- Improvement: Drilldown/Filters - the field dropdown will now display suggested fields at the top of the dropdown based on the reporting dimensions used in the insight.
- Improvement: GitHub Integration - Capture manually linked issues (through the GitHub UI) on top of issues referred to in PRs/commits via auto-closing keywords.
- Improvement: New template Historical in status at date - This new insight is similar to the āHistorical open at dateā, showing the number of issues that were in a specific status (or list of statuses) at a given date + moved in/out trends.
- Improvement: Dashboard Value Stream Management / Insights with custom dimensions - The drilldown has been updated on several insights to only display the records related to the clicked dimension.
- Bugfix: Drilldown - It is now possible to drilldown on null values
- Bugfix: Jira Integration - Add logic to detect and remove duplicate activity events. Jira sometimes generates duplicate changelog transition events for issues.
- Bugfix: Jira Integration - Add logic to resync child issues when a parent issue is updated. Jira silently updates child issues when a parent is updated (e.g. Sprint attribute)
- Bugfix: Dashboard Delivery / Deployment Frequency KPI - fixed the calculation to be dynamic based on the selected reporting period.
ā