Our Trello integration allows you to import project management data directly into Keypup to gain visibility on tasks, due dates and comments across multiple projects.
Data coming from Trello can be used to calculate metrics such as progress of a sprint, overdue items or display cards in customized listing or boards.
What data do we retrieve?
Our Trello integration fetches the following entities:
Cards
This entity is imported as an Issue on Keypup and exposed via the Issues & Pull Requests dataset. For each card, the name of the parent board column is imported as a label to facilitate filtering on the Keypup side. The issue (card) entity can be used to create activity metrics and listings.
E.g. calculate the Mean Time To Closure on bugs or incidents..
E.g. List all cards that are assigned to me.
Comments
This entity is exposed as a dataset on Keypup. Comments can be used to create a feed of updates or used to create activity metrics.
E.g. Recover and display comments of all open issues.
Labels
This entity is exposed as a field on the Issues & Pull Requests dataset. It is used to refine metrics and queries based on labels used in Trello.
E.g. Retrieve only issues which have the “bug” label.
How often do we refresh data?
Updates from Trello are received in real-time via webhooks.
If for any reason we are unable to set up real-time updates on Trello - e.g. the user who connected Trello has limited admin permissions in Trello - then we revert to long polling data every 20 minutes.
Whenever possible, we recommend connecting Trello as an admin to get the best experience on Keypup.
Improved reporting: Linking Issues to Pull Requests
Keypup uses context inference and link detection to automatically enrich your data, add news fields and simplify your reporting. All Keypup needs at time is a little hint, such as linking pull requests to issues in your development tools (GitHub, GitLab or Bitbucket) via auto-closing keywords.
How does it benefit my reporting?
Linking issues to pull requests allows us to populate and improve the following fields:
Issues & Pull Requests > Due on: When issues are linked to pull requests, Keypup automatically infers the due date by taking the soonest of all due dates across the pull request and its related issues.
Issues & Pull Requests > Resolution State: This field is only applicable to issues. It infers the implementation status of the issue by looking at the associated pull requests. The field can have the following values:
None: the issue has no attached pull requests. It is not being implemented.
In progress: the issue has at least one open pull request attached to it.
Implemented: all attached pull requests are merged or closed.
These two fields can be used to refine your metrics and/or drill down on specific data. E.g. Retrieve the list of overdue issues which - on top of that - are not being currently resolved by a pull request.
How to link issues to pull requests?
The easiest way is to reference the trello card URL from the body of your pull request using an auto-closing keyword such as fix, fixes, close, closes, resolve, resolves, for instance:
E.g. Closes https://trello.com/c/7bXwhvzb/1-email-taken-bug015