GitHub links
GitHub links
Breadcrumbs

Engineering Reporting - Troubleshooting and FAQ

My chart is empty or showing no data

Check your date range. Try widening it - if there is little PR activity in a narrow window, the macro may have nothing to display.

Check your repository selection. Confirm the correct repositories are selected in the macro configuration. Repositories the GitHub App cannot access will not appear in the selector.

Wait and re-render. Computed aggregates are cached for 12 minutes. If the page was loaded during a brief GitHub API issue, re-loading the page after a short wait should refresh the result.

GitHub scopes and permissions

The Reporting Macros reuse your existing GitHub App connection - no new GitHub scopes are required to start using them.

If a repository shows no data, confirm the GitHub App connection has access to that repository. See Managing GitHub App permissions and organisation access.

If your organisation's GitHub connection was recently changed or re-authorised, you may need to reconnect via Confluence Administration > Apps > GitHub. See Connecting and disconnecting GitHub links.

GitHub API rate limits

The Reporting Macros make live GitHub API calls on each page render. The short-TTL aggregate cache reduces repeat calls, but heavy usage can still approach rate limits.

If you hit a rate limit:

  • Wait briefly and re-render the page.

  • Avoid placing a large number of reporting macros with very wide date ranges on a single page.

Private repositories

Private repositories are fully supported if your existing GitHub App connection has access to them. No source code or PR content is stored - only computed aggregates are cached briefly.

If a private repository shows no data, verify that the GitHub App has been granted access to it. See Managing GitHub App permissions and organisation access.

Frequently asked questions

Can I see per-developer metrics?
No. All metrics are team-level only - aggregated across the selected repositories. Per-developer breakdowns are not available and are not planned for v1.

Is this a full DORA implementation?
No. The macros provide DORA-style delivery metrics: PR Cycle Time, PR Throughput, and Review Latency. Change Failure Rate (CFR) and Mean Time to Recovery (MTTR) are not included in v1.

Does this cost extra?
No. Engineering Reporting is included in the app at your standard subscription - no separate pricing.

Where is macro configuration stored?
As standard Confluence macro parameters on the page. Nothing is stored outside Confluence.

Does the app store our code or PR data?
No. Metrics are computed live from the GitHub API. Only the computed aggregate is cached briefly. See What we store (reporting) for full detail.

Do I need to set up a new GitHub connection?
No. The Reporting Macros reuse your existing GitHub App connection. No new scopes or permissions are required to start.

Can I filter by branch?
Branch filtering is not available in v1. All branches accessible to the GitHub App connection are included in results.

Updated: