Now, you can break down metrics into more actionable components to get insights even if you use a monorepo.
All you need to do is add some kind of identification to your PRs so Athenian can filter to create a logical representation of the components that form your repo.
You can do so in 4 easy steps plus an optional one:
Auto-label your PRs with a logical component identification
Apply to historical data
Share your components with us
Configure your releases per logical repo
[Optional] Configure your deployments per logical repo
We go in-depth on how to do so here.
Single Sign-On just got better for our Premium Plan customers.
Athenian now allows users to sign up via SSO without an invitation link.
This means that if your company uses Identity Management to manage your workforce's access to company tools, you don't have to send a link to each one for them to sign up anymore.
👉 Any new member will now have access to Athenian instantly via SSO.
We also made it possible to disable sign up via GitHub and only keep SSO.
❗️Please keep in mind that for your company to have access to SSO it must be on our Premium Plan.
Athenian has been formally attested as SOC 2 Type 2 compliant for how we securely manage user data based on our service and organizational controls.
The SOC 2 Type 2 report without exceptions is a badge of excellence and formal evidence of Athenian's commitment to securely handling customers' data and keeping it safe under the highest industry standards. Simply put: you can trust Athenian with your data.
Read more about the announcement here.
More information about how we take security measures and requests for our security documentation, including our SOC 2 Type 2 report can be found in our Security Page.
To leverage even more the connection between GitHub and Jira that you have in Athenian, we have enhanced how PRs are mapped to Jira issues.
Our platform now searches for Jira issues IDs in the PR's branch name as well.
This means that even if the issue ID is not in the title or body (which is recommended), but it is in the branch name, the PR will be mapped to the corresponding ticket.
This improvement is directly linked to better alignment between your Engineering and Product teams, bringing more transparency into what's being done and into delivery expectations.
👉 All accounts already have this improvement installed.
In the new Deploy section, users can now see beyond insights and dig into the underlying data available through the Pull Requests table.
As other sections, you will now find the PRs related to this stage right next to your Ingishts graphs. This time, the data is filtered by environment according to the ones your organization has set up.
Please note that the PRs listed in the table are only from the repos you are sending us deploy data.
👉 This table is useful to identify outliers or patterns in your engineering organization.
If you haven't set up your Deploy metrics yet, check out how to do so here.
We're very excited to announce our new Training Program for current and new users of Athenian.
This program is designed to help you learn the basics of Athenian and apply them in your day-to-day. All this under 30 minutes!
What you get:
Detailed descriptions and videos to walk you through each section of the product
Explanations about how metrics are calculated
Tips on how to interpret the data
Questions you should ask about the data you see in the dashboard
Recommendations on what to improve
If you're a new user, this training program will help you answer your questions and get started on using Athenian.
If you're already an user, it will refresh your skills and help you find new ways to use the product.
We're happy to announce a new sub-section in your Delivery Pipeline available to all users of Athenian: Deploy.
→ Check out this article about how to unlock Deployment Metrics at Athenian.
The deployment is the last step before a PR is live in front of customers. It has the biggest impact on user experience and on the business.
Located under the Delivery Pipeline on your side bar, this sub-section provides you the Deployment Frequency, which is how often new code changes are deployed; and PR Cycle Time.
These metrics are grouped for each environment of your organizational structure so you can assess whether there are bottlenecks when promoting PRs from an environment to another.
You will also find the Time To Deploy, the Number of Deployments in comparison to the number of PRs and the Success Ratio of your deploys.
As always, it is also possible to see your progress in a timeline and the distribution over time for a deeper analysis.
In this sub-section you can filter the data by date range, teams, and repos.
Sharing your dashboard with peers just became easier. No more screenshots, or discussions about which filters to apply to see the same insights.
You can now easily share exactly what you see in your Athenian dashboard with any company peer in just one click.
When you're at the section you would like to share, click on “Share this view” on the top right corner of the page.
A unique link will be automatically generated and copied to your clipboard.
Simply share the link with other users of Athenian in your company.
→ All links are unique so you can easily revisit shared views whenever and as many times as you and your team would like.
→ Be aware that once you click on a link, it will override your current view. Make sure to save a link with your current view before clicking on a new one.
In Allocation, now it is possible to filter the data according to an organization's own Jira labels, besides Github Labels and Issue Types.
To configure, the user should go to Settings > Allocation and Add Rule > Jira Label to the Work Type they would like to be linked to that label(s).
This way, the user will see the data in Allocation By Work Type considering the Jira Labels.
The organisation uses Jira labels to classify PRs by what they call Product Theme, which includes labels such as Usability, Reliability, Accuracy, Performance, etc.
After creating the new rules, they can filter Allocation by Work Type to show in the graph the Work Types linked to the Product Theme only. This way, they can assess the effort their teams are putting into each pre-defined category (label).
This functionality also facilitates usage since, from now on, there is no need to send GitHub labels to Jira to assess the data in Athenian.
NOTE: This improvement does not support Jira custom fields.
Users who use different naming for their Epics can now see them in the Epics Table classified as such, even if with different naming.
Before, Athenian only showed an Epic that was named as such in Jira, missing out on “other Epics” which were renamed by the user. Now all issues classified as Epics on Jira, with or without such name, are shown as Epics in Athenian.
This helps the user have a clearer view of the workload with the right classification of issues, tasks, subtasks etc.