The Keypup platform enforces several limits to maintain the stability and performance of the platform. These limits are detailed below.
Chart plotting
Charts will load 10,000 data points by default, in a paginated way. This limit is configurable via the insight edition screen (Configure Table/Trend section). Please be aware that increasing the limit will slow down the loading of the chart.
Multi-series charts (e.g., Line Chart 2-dimensional) are limited to 100 series. Beyond this limit, an error will be displayed on the insights.
Heatmap charts are limited to 10,000 cells. Beyond this limit, an error will be displayed on the heatmap.
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…).
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...
Number of custom fields
The Keypup user interface loads a maximum of 2000 custom fields across all applications.
Using more custom fields? Contact us via chat or via [email protected]
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...