Skip to main content
FAQ - Frequently Asked Questions

Athenian Frequently Asked Questions

Paul Bleicher avatar
Written by Paul Bleicher
Updated over a week ago

Do you have the ability to backfill data, i.e. metrics from past tickets, or is it only on a go-forward basis? If so, is there a limitation to how far you can backfill?

We load and compute metrics based on all the historical data without any limitation. 15 months of data can be queried inside Athenian.

Do you support GitHub Enterprise and/or Jira Server?

Yes, we support both GitHub Enterprise and Jira Server. While our product is cloud-based, we can securely connect to your on-premise installations of GitHub and Jira.

Is Athenian secure?

Security is a top priority for us.

  • We only ask the most essential permissions to provide you insights

  • Metrics come from metadata and we never store source code

  • The data processed is fully encrypted in transit and at rest

  • All key providers are SOC 1/2/3, ISO27001, and/or PCI compliant

Do you support Gitlab, Bitbucket or Azure DevOps?

Not yet! Gitlab, Bitbucket and Azure DevOps support is on our roadmap. Register your interest on our feature request board to be the first to know when they are available.

How do I add more repositories to Athenian?

To add new repositories to Athenian, just head over to the Athenian Github app and select the repositories you want to add. The data will start to appear in your dashboard after a couple of hours to a few days depending on the number of repositories added.

Do you consider weekends or only business hours for the data?

Our data considers full calendar time. What we see in the industry as a best practice is to consider full calendar time. If, for example, the weekends pose an issue for code reviews. By using all hours of the week we can see that teams are considering work done as the end of individual development tasks, and not their responsibility of optimizing for team tasks' progress. By pushing lots of reviews to the end of the week teams are not following a good flow, a key element for efficiency.

For a given time range, what determines which tickets are considered in progress and/or completed?

For a given time range, a ticket is considered:

  1. In progress when the ticket is moved to an In Progress Jira status category (blue status in Jira)

  2. Done when the ticket is moved to a Done Jira status category (green status in Jira) or when all the matching PRs are released. The or relation here is a max()

Did this answer your question?