Managing Release Control Reports and Notifications

Reports and notifications help keep release management stakeholders informed of status, history, and other release information. Serena Release Control provides a default set of reports and notifications, and you can configure these as needed to support your organization.

Configuring Reports

Some of the Serena Business Manager reports are used to populate the Serena Release Control user interface views. You can configure those as documented in Customizing the User Interface.

In addition to reports used for the UI views, you can configure general reports to provide the information you need for your organization’s release control.

The general reports configured by default for Serena Release Control are shown in the following table.

Objects

Reports

Description

Release Trains

Dashboard

A multi-view report for the Dashboard page. See Customizing the Serena Release Control Dashboard.

Inactive RTrains

All inactive release trains.

Inactive Release Trains

All release trains that are in inactive status.

Release train by type

Release trains by type.

Release Trains in Gantt

Release trains in a Gantt-style format, used for the Calendars page. See Configuring the Calendar.

Train All

All release trains.

train Assigned To Current User

All release trains assigned to the current user, used for the My Inbox page. See Configuring the Inbox.

Application Releases

Application releases by application and type

Application releases by application and type.

Application All

All application releases.

application Assigned To Current User

Application releases assigned to the current user, used for the My Inbox page. See Configuring the Inbox.

Application Releases In Release Train

Application releases in the selected release train.

Application Releases Unassigned

Application releases that are not yet assigned to release trains.

Inactive Application Releases

Application releases that are in inactive status.

Release Packages

Inactive Release Packages

All release packages that are in inactive status.

Package All

All release packages.

package Assigned To Current User

Release packages assigned to the current user, used for the My Inbox page. See Configuring the Inbox.

Release Packages in Application Release

Release packages in the selected application release.

Release packages list by owner

Release packages list by owner.

Unassigned Release Packages

Release packages that are not yet assigned to application releases.

Deployment Tasks

all DT

All deployment tasks.

Assigned Tasks

Deployment tasks assigned to the selected release package stage.

Deployment task I own

Deployment tasks owned by the current user.

task All

All deployment tasks.

task Assigned To Current User

Deployment tasks assigned the current user, used for the My Inbox page. See Configuring the Inbox.

Template Tasks

Tasks in the selected deployment process template.

Environment

Environment in Release Packages

All environments in the selected release package.

Environments All

All environments.

Environments owned by current user

Environments owned by the current user.

Environments Commissioned

All environments in the commissioned state.

Inactive Environments

All inactive environments.

Others

All Release Type Stages

All stages sorted by release type and sequence.

All Stages

All stages defined in Serena Release Control.

Assigned Business Change Requests

Business change requests

associated with the selected application release.

Assigned Deployment Units

Deployment units associated with the selected release package.

Assigned Development Change Requests

Development change requests associated with the selected release package.

Assigned Requests for Change

Requests for change associated with the selected release train.

DCR Projects Assigned to a Release Package

Development change requests associated with the selected release package.

Dimensions CM Projects Assigned to a Release Package

Dimensions CM projects associated with the selected release package.

Stages in Release Type

All stages for the selected release type.

ZMF Projects Assigned to a Release Package

ZMF projects, or applications, associated with the selected release package.

What Can You Change?

You can change the following report information:

What is the Impact?

How Do You Change It?

You can manage reports from the Serena Release Control standard SBM user interface according to the SBM documentation.

 

 

NOTE  End users with the proper privileges can add reports from the Reports view in the Serena Release Control UI shell by editing a report and using the Save As option to save it to another report name. However, only Serena Release Manager administrators should be given the privileges to modify reports provided with Serena Release Control.

Documentation References

Complete documentation on configuring SBM reports is in the Serena Business Manager User’s Guide in "Working with Reports".

Configuring Notifications

E-mail notifications are sent to Serena Release Control users to alert them of actions requiring their attention, provide important status information on releases, and so on.

The e-mail notifications configured by default for Serena Release Control are shown in the following table.

Entity

Notifications

Release Train

RTN - Any Release Train changes owner

RTN - Any Release Train changes state

RTN - Any Release Train changes to inactive

RTN - Any Release Train I submitted changed state

RTN - Any Release Train I submitted changed to inactive

RTN - Any Release Train is submitted

RTN - I become the owner of any Release Train

Application Release

AR - Any Application Release changes owner

AR - Any Application Release changes state

AR - Any Application Release changes to inactive

AR - Any Application Release I submitted changed state

AR - Any Application Release I submitted changed to inactive

AR - Any Application Release is submitted

AR - I become the owner of any Application Release

Release Package

RP - Any Release Package changes owner

RP - Any Release Package changes state

RP - Any Release Package changes to inactive

RP - Any Release Package I submitted changed state

RP - Any Release Package I submitted changed to inactive

RP - Any Release Package is submitted

RP - I become the owner of any Release Package

Deployment Task

D - Any Automation Task fails for Release Engineer or Manager

D - Any Vault Task fails for Release Engineer or Manager

D - Any Deployment changes owner

D - Any Deployment changes state

D - Any Deployment changes to inactive

D - Any Deployment I submitted changed state

D - Any Deployment I submitted changed to inactive

D - Any Deployment is submitted

D - I become the owner of an In Progress Automation Task

D - I become the owner of an In Progress Manual Task

D - I become the owner of an In Progress Vault Task

D - I become the owner of any Deployment

Deployment Process Template

RT - Any Release Template changes owner

RT - Any Release Template changes state

RT - Any Release Template changes to inactive

RT - Any Release Template I submitted changed state

RT - Any Release Template I submitted changed to inactive

RT - Any Release Template is submitted

RT - I become the owner of any Release Template

Other (Auxiliary)

RA - Any Rlm Aux changes owner

RA - Any Rlm Aux changes state

RA - Any Rlm Aux changes to inactive

RA - Any Rlm Aux I submitted changed state

RA - Any Rlm Aux I submitted changed to inactive

RA - Any Rlm Aux is submitted

RA - I become the owner of any Rlm Aux

Development Change Request (DCR): SBM Incident

I - Any Incident changes owner

I - Any Incident changes state

I - Any Incident changes to inactive

I- Any Incident I submitted changed state

I - Any Incident I submitted changed to inactive

I- Any Incident is submitted

I - I become the owner of any Incident

Business Change Request (BCR): SBM Issue

I - Any Issue changes owner

I - Any Issue changes state

I - Any Issue changes to inactive

I- Any Issue I submitted changed state

I - Any Issue I submitted changed to inactive

I- Any Issue is submitted

I - I become the owner of any Issue

Development Change Request (DCR): Dimensions CM Request

RV - Any Change Request changes owner

RV - Any Change Request changes state

RV - Any Change Request changes to inactive

RV - Any Change Request I submitted changed state

RV - Any Change Request I submitted changed to inactive

RV - Any Change Request is submitted

RV - I become the owner of any Change Request

Request for Change (RFC): SSM CAR

CAR - Any Change Request changes owner

CAR - Any Change Request changes state

CAR - Any Change Request changes to inactive

CAR - Any Change Request I submitted changed state

CAR - Any Change Request I submitted changed to inactive

CAR - Any Change Request is submitted

CAR - I become the owner of any Change Request

Environment

E - Any Environment changes owner

E - Any Environment changes state

E - Any Environment changes to inactive

E - Any Environment I submitted changed state

E - Any Environment I submitted changed to inactive

E - Any Environment is submitted

E - I become the owner of any Environment

What Can You Change?

You can modify the provided notifications and configure additional notifications as needed to support your release management processes.

Notifications in SBM are e-mail messages sent to users when certain events or conditions occur in the system. Notifications can also be used to automatically add and remove items from folders and to execute scripts.

You can change the following notification information:

What is the Impact?

If you add a notification, you must subscribe users to it so that they will be sent to them upon the event associated with the notification.

How Do You Change It?

You can manage notifications in SBM System Administrator according to the SBM documentation.

Documentation References

Complete documentation on configuring SBM notifications is in the Serena Business Manager System Administrator Guide in "Managing Notifications".