Post Integration Configurations

Valven Atlas offers capabilities to analyze the software development cycle and offers additional features to ensure resource distribution is monitored correctly and business alignment is established between executives and the teams. 

In order to benefit from all the Valven Atlas features, there are additional configurations to enable the solution to align with your organization's patterns. In this document, we will cover additional settings that will enable you to get the best out of Valven Atlas.

The post-integration configurations are placed at the bottom of the sidebar under the profile page > Settings option.

Company Settings

In the company settings, you can provide your working habits based on the working days, hours as well as the timezone for the reports to be shown properly. 

Additionally, you can register the average man-day cost for Valven Atlas to calculate the investment in correlation to the effort your team puts in. 

It is also possible to enable Two-Factor Authentication for your company users to sign in to their accounts more securely. By simply enabling the Two-Factor Authentication switch, you can initiate a process where each user will get a second phase of authentication through their registered email.

Teams

Teams can be imported from the team architecture of GitHub, GitLab, Linear, and Youtrack or manually created from Valven Atlas.

After importing or adding the teams, contributors can be associated with the corresponding teams to have the analysis and resource distribution based on different teams. 

By clicking the three-dot icon at the right side of each team record you can open the contributor list where you can make modifications to the selections. 

Configurations

On the configurations page, you can categorize your issue types and status types into predefined areas in Valven Atlas so that Valven Atlas can provide reports in each category including the time in each state or analyze the resources work each work type.

Valven Atlas applies some basic categorization for statuses of Open, In Progress, and Closed. Under each issue or status map, you will be presented with an option to categorize your issues or statuses based on either the type or the label you define for the issues. 

The conditions you set will define how Valven Atlas evaluates the data and presents it in the reports and insights to create a perfectly matching case for your software development cycle design. 

Outliers

Valven Atlas also offers a way to exclude the desired commits and pull requests from the calculations with Outliers. 

In some cases, organizations may choose to eliminate some changes containing a large amount of file changes or open PRs with specific titles. In the outliers section, you can easily define such pull requests or commits by providing expressions for titles or messages matching your case or based on the label you use. 

DORA 

Even when there is no active CI/CD integration, Valven Atlas offers an option to mark releases to provide an analysis of the deployment process in the software development lifecycle.

There are three configurations to detect the releases, failures, and recovery actions. 

Release Detection

Release detection enables Valven Atlas to provide one of the critical indicators of DORA metrics: deployment frequency. 

Valven Atlas can detect releases based on the Git Tags, pull requests to be merged, or the destination branches that the pull requests are merged. 

On the DORA section of the settings page, the release detection option enables Valven Atlas users to define the release actions so that Valven Atlas can understand the releases and provide analysis on the DORA metrics. 

How does Release Detection work?

Failure Detection

Failure detection is used for Change Failure Rate(CFR) reports to provide the percentage of deployments that fail in production. 

The related pull requests or issues should be marked with the same identifiers in their title, header, or description for Valven Atlas to detect faulty releases.

As the second option of the DORA settings section, the failure detection option enables Valven Atlas users to define the failed releases so that Valven Atlas can identify such releases and provide analysis on the DORA metrics. 

How does Failure Detection work?

Recover Detection

Recover detection is used to calculate the mean time to recover. The issues and pull requests with defined titles or descriptions will be evaluated as actions to recover and you can also define a destination branch for Valven Atlas to categorize the pull request as a recovery.

As the last option of the DORA settings section, the recover detection option enables Valven Atlas users to define the actions and improvements applied to recover from faulty releases so Valven Atlas can identify such actions and provide analysis on the time and effort to recover.

How does Recover Detection work?