The Keypup platform enforces several limits to maintain the stability and performance of the platform. These limits are detailed below.
Data export
System limit
Data exports are limited to 500 records. This means that 500 data points from the chart or report will be returned at most.
How to handle this limit
You can work around this limit by using filters to restrict the range of data to report on (e.g. decrease the time range, focus on specific projects or labels to focus on) or changing to a wider granularity (e.g. group dates by months rather than weeks or days) expectedly gives good results.
Links between Issues and Pull requests
Keypup supports the discovery of Issue-to-PR relationships via auto-closing keywords. Issue-to-PR relationships are useful for cross-entity queries (e.g. filter pull requests based on issue labels, or use issue creation date at the pull request level…).
System limit
The issue-to-PR relationship discovery is limited to 50 issues for each pull request and 50 pull requests for each issue. The ranking strategy is different for issues and PRs.
> For Issues (resolving PRs)
Resolving PRs are sorted by order of creation and deduplicated. On the resulting list, the first 50 PRs are retained.
> For Pull Requests (resolved issues)
To determine the ranking of resolved issues, Keypup scans for auto-closing keywords in a specific order of precedence.
Order of precedence:
Branch Name: We look for issue keys in the branch name (reading from left to right).
PR Title: Then we look in the PR title (reading from left to right).
PR Body: Then we look in the PR description/body (reading from left to right).
Commits: Finally, we scan the commit messages associated with the PR, ordered chronologically (older to newer) and from left to right.
The first 50 PRs are retained and then deduplicated.
How to handle this limit
Having 50+ associated issues for a single pull request generally means a release or rebase PR has been left open for quite some time and should be considered an outlier.
Length of Issue/PR descriptions
PR and Issue descriptions are limited to 10,000 characters to maintain reasonable system performance.
Values exceeding this content will be truncated to 9997 characters and terminated with an ellipsis (...)
E.g. some really really long description with...
Length of custom field attributes
The value of custom fields (e.g. Jira custom fields) attributes is limited to 200 characters. In the case of complex fields with embedded objects, this value applies to each embedded object attribute (e.g. "fix versions > object > description")
Values exceeding this content will be truncated to 197 characters and terminated with an ellipsis (...)
E.g. some really really long content with...