Release Update 01/25/2024

SDLC and DevOps

Automatically updating Git credentials within the Jenkins tool

Configuring Git credentials in Jenkins is critical for automating the build, deployment, and continuous integration processes in your SDLC pipeline. We've noticed that the associated Jenkins operation fails when a customer modifies their Git password or token after it expires. This Git Authentication failure leads to Jenkins jobs failing, which in turn causes pipeline issues.

With this most recent version, Opsera updates the credentials whenever a token or password change occurs in the Git Tool Registry and locates the list of Jenkins using the appropriate Git Tool. This update ensures that the vault's most recent Git credentials are used during the task execution phase.

For more info, read here.

Capability to associate security policies for Wiz Security Scan.

When using Wiz Scan in their CI/CD Workflow, users can specify their organization's security policy. Users must enter their specific security policy while configuring the Pipeline step.

By default, the security policy associated with the Wiz tool used in the Pipeline step will be applied during the scan. This assists organization members by allowing them to review the specific policy document that contains the goals, responsibilities, structure of the security programme, compliance, and risk management strategy. For more info, read here.

IAM authentication for the AWS Tool Connection

Opsera provides an additional method of connection establishment for the AWS Tool that uses IAM authentication. When this authentication mode is selected, Opsera creates an IAM Role trust entity, and users with IAM roles can securely connect using their ARN role and AWS region. Apart from utilizing AWS ID and secret access keys, this method enables you to securely connect your AWS account to Opsera. For more info, read here.

Support for JSON input in Argo application creation.

When creating an Argo application in Opsera, users can include JSON data. When creating an Argo app associated with Helm charts, you can upload data in JSON format. For more info, read here.

Insights

Calculate Jira Velocity based on Story Points

Previously, the say-do ratio was determined by comparing the committed and completed values of various Jira issue types. Similarly, the velocity was determined by counting the number of issues finished within a sprint.

Going forward, the Say Do Ratio calculation will be based on delivered story point and committed story point, and the Velocity calculation will be based on Story points completed. Calculations based on story points are a more refined method of estimating work than time-based metrics like hours or days.

It should be noted that the velocity charts will display the updated data if the story points are modified after the sprint has begun.

For more info, read here.

Jira Input Fields are Modified to a Drop Down List

Previously, users would enter their Jira statuses based on the Jira processes in the "Jira Issue Done Status" field of the Jira KPIs. Now, the input field is converted into a list that retrieves data based on the values selected from the list and displays the Jira workflow statuses. In addition, the "Jira Issue Start Status" input field in the Jira Lead Time KPI is changed to a list of workflow values.

This change is implemented in the following KPIs: Jira Lead Time, Jira Sprint Burndown, Jira Velocity, and Jira Defect Density.

For more info, read here.

Send dashboards as email reports

• Set up periodic email reports with details from one or more dashboards. These reports can be sent once or on a regular basis to multiple email addresses. This allows you to share dashboard views in your workspaces with other non-users by emailing them.

  
• As of the most recent update, the email report subject lines will include the Dashboard names.

  

For more info, read here.