Understanding the DevOps Insight Data Model

This section describes the DevOps Insight data model. It is comprised of several interrelated schemas that are externalized as report object types. Topics in this section include:

Data Model Overview

The DevOps Insight data model consists of several report object types as represented by this diagram:

The data in each type is sourced as described in the below table. Click on an object type for complete details about its structure.

Report Object Type	Managed by	Notes
Build	EC-Jenkins plugin	Data derived directly from the Build plugin with contributions from the BuildCommit and Quality plugins.
Build Commit	EC-Jenkins plugin	Data derived directly from the plugin.
Code Commit	ECSCM-Git plugin	Data derived from `BuildCommit ` plugin.
Defect	EC-JIRA plugin	Data derived directly from the plugin.
Deployment	CloudBees CD	Data derived from directly from CloudBees CD.
Feature	EC-JIRA plugin	Data derived directly from the plugin.
Incident	EC-ServiceNow plugin	Data derived directly from the plugin.
Job	CloudBees CD	Data derived from directly from CloudBees CD.
Pipeline Run	CloudBees CD	Data derived from directly from CloudBees CD, with contributions from Deployment.
Quality	EC-ALM plugin	Data derived directly from the plugin.
Release	CloudBees CD	Feature, Defect, Incident, PipelineRun, Deployment, Quality, and Build report object types contribute to data in this object

Report Object Type

Managed by

Notes

Build

EC-Jenkins plugin

Data derived directly from the Build plugin with contributions from the BuildCommit and Quality plugins.

Build Commit

EC-Jenkins plugin

Data derived directly from the plugin.

Code Commit

ECSCM-Git plugin

Data derived from `BuildCommit ` plugin.

Defect

EC-JIRA plugin

Data derived directly from the plugin.

Deployment

CloudBees CD

Data derived from directly from CloudBees CD.

Feature

EC-JIRA plugin

Data derived directly from the plugin.

Incident

EC-ServiceNow plugin

Data derived directly from the plugin.

Job

CloudBees CD

Data derived from directly from CloudBees CD.

Pipeline Run

CloudBees CD

Data derived from directly from CloudBees CD, with contributions from Deployment.

Quality

EC-ALM plugin

Data derived directly from the plugin.

Release

CloudBees CD

Feature, Defect, Incident, PipelineRun, Deployment, Quality, and Build report object types contribute to data in this object

Report Object Type Reference

You use attributes for DevOps Insight report objects when creating custom reports and dashboards. The following tables list the attributes for the DevOps Insight report object types.

Build

Object Type: Build Report object name: build Description: Build data from Jenkins or CloudBees CD.

Object Type: Build Report object name: build Description: Build data from Jenkins or CloudBees CD.
Attribute	Display Name	Type	Description
baseDrilldownUrl	Base Drilldown Url	`STRING`	Base URL used to construct the full URL for drilling down from a widget into an external build system such as Jenkins. For example, `https://10.200.1.171:8080/job/CrossWing.`
buildNumber	Build Number	`STRING`	Unique build number or identifier assigned to the build by the build system.
buildStatus	Build Status	`STRING`	Current status of the build: `SUCCESS`, `FAILURE`, `UNSTABLE` (Jenkins only), `NOT_BUILT`, `ABORTED`, or `WARNING.`
duration	Duration	`NUMBER`	Duration of the build in milliseconds
endTime	End Time	`DATETIME`	End date and time for the build. The format is ISO 8601 in UTC time. For example, `2017-01-01T11:54:58.569Z`.
launchedBy	Launched By	`STRING`	User or process that launched the build.
pluginConfiguration	Plugin Configuration	`STRING`	Name of the plugin configuration if the data was populated through EC-Jenkins.
pluginName	Plugin Name	`STRING`	Name of the plugin if the data was populated through a plugin such as EC-Jenkins. For example, `EC-Jenkins.`
projectName	Build System Project Name	`STRING`	Name of the project in the build system. For example, the Jenkins project name for Jenkins builds, the CloudBees CD project name for ElectricSentry builds, or the build project name in TFS.
releaseName	Release Name	`STRING`	Name of the CloudBees CD release to which the build belongs.
releaseProjectName	Release Project Name	`STRING`	Name of the CloudBees CD project containing the release to which the build belongs.
releaseUri	Release URI	`STRING`	Partial URL that can be used along with `baseDrilldownUrl` to construct the drill-down URL to navigate to builds associated with the current release. The continuous integration system must allow such URLs. For Jenkins, DevOps Insight does not use this field, because Jenkins does not provide this ability. You can drill down only into the builds of a specific project in Jenkins.
source	Build System Type	`STRING`	Name of the continuous integration system. For example, `Jenkins.`
sourceUrl	Build URL	`STRING`	URL for the build record. For example, `https://10.200.1.171:8080/job/CrossWing.`
startTime	Start Time	`DATETIME`	Starting date and time for the build. The format is ISO 8601 in UTC time. For example, `2017-01-01T11:54:58.569Z`.
tags	Tags	`STRING`	Tags or labels associated with the build.
timestamp	Timestamp	`DATETIME`	Date and time that the build completed. The system uses this field to determine the time-based index for storing the build record by year. For example, builds that completed in 2017 are stored in the index `ef-build-2017`. The format is ISO 8601 in UTC time. For example, `2017-01-01T11:54:58.569Z.`
jobName	Job Name	STRING	Name of the Job. For CloudBees CD CI builds, this will be set using the name of the job started by ElectricSentry to do the build. Not used for Jenkins builds.

Attribute

Display Name

Type

Description

baseDrilldownUrl

Base Drilldown Url

STRING

Base URL used to construct the full URL for drilling down from a widget into an external build system such as Jenkins. For example, https://10.200.1.171:8080/job/CrossWing.

buildNumber

Build Number

STRING

Unique build number or identifier assigned to the build by the build system.

buildStatus

Build Status

STRING

Current status of the build: SUCCESS, FAILURE, UNSTABLE (Jenkins only), NOT_BUILT, ABORTED, or WARNING.

duration

Duration

NUMBER

Duration of the build in milliseconds

endTime

End Time

DATETIME

End date and time for the build. The format is ISO 8601 in UTC time. For example, 2017-01-01T11:54:58.569Z.

launchedBy

Launched By

STRING

User or process that launched the build.

pluginConfiguration

Plugin Configuration

STRING

Name of the plugin configuration if the data was populated through EC-Jenkins.

pluginName

Plugin Name

STRING

Name of the plugin if the data was populated through a plugin such as EC-Jenkins. For example, EC-Jenkins.

projectName

Build System Project Name

STRING

Name of the project in the build system. For example, the Jenkins project name for Jenkins builds, the CloudBees CD project name for ElectricSentry builds, or the build project name in TFS.

releaseName

Release Name

STRING

Name of the CloudBees CD release to which the build belongs.

releaseProjectName

Release Project Name

STRING

Name of the CloudBees CD project containing the release to which the build belongs.

releaseUri

Release URI

STRING

Partial URL that can be used along with baseDrilldownUrl to construct the drill-down URL to navigate to builds associated with the current release. The continuous integration system must allow such URLs. For Jenkins, DevOps Insight does not use this field, because Jenkins does not provide this ability.

You can drill down only into the builds of a specific project in Jenkins.

source

Build System Type

STRING

Name of the continuous integration system. For example, Jenkins.

sourceUrl

Build URL

STRING

URL for the build record. For example, https://10.200.1.171:8080/job/CrossWing.

startTime

Start Time

DATETIME

Starting date and time for the build. The format is ISO 8601 in UTC time. For example, 2017-01-01T11:54:58.569Z.

tags

Tags

STRING

Tags or labels associated with the build.

timestamp

Timestamp

DATETIME

Date and time that the build completed. The system uses this field to determine the time-based index for storing the build record by year. For example, builds that completed in 2017 are stored in the index ef-build-2017.

The format is ISO 8601 in UTC time. For example, 2017-01-01T11:54:58.569Z.

jobName

Job Name

STRING

Name of the Job. For CloudBees CD CI builds, this will be set using the name of the job started by ElectricSentry to do the build. Not used for Jenkins builds.

Build Commit

Object Type: Build Commit Report object name: build_commit Description: Source code changesets included in builds done by CloudBees CD or Jenkins continuous integration system.

Object Type: Build Commit Report object name: build_commit Description: Source code changesets included in builds done by CloudBees CD or Jenkins continuous integration system.
Attribute	Display Name	Type	Description
buildUrl	Build URL	`STRING`	URL for the build record. For example, `https://10.200.1.171:8080/job/CrossWing`
buildNumber	Build Number	`STRING`	Unique build number or identifier assigned to the build by the build system
startTime	Start Time	`DATETIME`	Start date and time for the build. The format is ISO 8601 in UTC time. For example, `2017-01-01T11:54:58.569ZÂ`
endTime	End Time	`DATETIME`	End date and time for the build. The format is ISO 8601 in UTC time. For example, `2017-01-01T11:54:58.569ZÂ`
buildStatus	Build Status	`STRING`	Current status of the build: `SUCCESS`, `FAILURE`, `UNSTABLE` (Jenkins only), `NOT_BUILT`, `ABORTED`, or `WARNING`
projectName	Build System Project Name	`STRING`	Name of the project in the build system. For example, the Jenkins project name for Jenkins builds, the CloudBees CD project name for CloudBees CD CI builds, or the build project name in TFS
tags	Tags	`STRING`	Tags or labels associated with the build
buildSource	Build System Type	`STRING`	Name of the continuous integration system. For example, `Jenkins`
commitDate	Commit Date	`DATETIME`	Date when the changeset was committed or checked into the source control system.
commitId	Commit ID	`STRING`	Unique identifier for the changeset in the source control management system. For example, SHA number in Git or changelist number in Perforce
commitUrl	Commit URL	`STRING`	URL to the changeset in the SCM repository
jobName	Job Name	`STRING`	Name of the Job. For CloudBees CD CI builds, this will be set using the name of the job started by ElectricSentry to do the build. Not used for Jenkins builds
scmRepoBranch	SCM Repository Branch	`STRING`	Repository branch—Specific to Git or Git-based SCMs. For example, `‘master’`
scmSource	SCM Type	`STRING`	Name of the source control management system. For example, `Git` or `Perforce`
scmUrl	SCM Server URL	`STRING`	URL to the SCM repository or the SCM server name. For example, `'git://git.apache.org/zookeeper.git'`

Attribute

Display Name

Type

Description

buildUrl

Build URL

STRING

URL for the build record. For example, https://10.200.1.171:8080/job/CrossWing

buildNumber

Build Number

STRING

Unique build number or identifier assigned to the build by the build system

startTime

Start Time

DATETIME

Start date and time for the build. The format is ISO 8601 in UTC time. For example, 2017-01-01T11:54:58.569ZÂ

endTime

End Time

DATETIME

End date and time for the build. The format is ISO 8601 in UTC time. For example, 2017-01-01T11:54:58.569ZÂ

buildStatus

Build Status

STRING

Current status of the build: SUCCESS, FAILURE, UNSTABLE (Jenkins only), NOT_BUILT, ABORTED, or WARNING

projectName

Build System Project Name

STRING

Name of the project in the build system. For example, the Jenkins project name for Jenkins builds, the CloudBees CD project name for CloudBees CD CI builds, or the build project name in TFS

tags

Tags

STRING

Tags or labels associated with the build

buildSource

Build System Type

STRING

Name of the continuous integration system. For example, Jenkins

commitDate

Commit Date

DATETIME

Date when the changeset was committed or checked into the source control system.

commitId

Commit ID

STRING

Unique identifier for the changeset in the source control management system. For example, SHA number in Git or changelist number in Perforce

commitUrl

Commit URL

STRING

URL to the changeset in the SCM repository

jobName

Job Name

STRING

Name of the Job. For CloudBees CD CI builds, this will be set using the name of the job started by ElectricSentry to do the build. Not used for Jenkins builds

scmRepoBranch

SCM Repository Branch

STRING

Repository branch—Specific to Git or Git-based SCMs. For example, ‘master’

scmSource

SCM Type

STRING

Name of the source control management system. For example, Git or Perforce

scmUrl

SCM Server URL

STRING

URL to the SCM repository or the SCM server name. For example, 'git://git.apache.org/zookeeper.git'

Code Commit

Object Type: Code Commit Report object name: code_commit Description: Code commit or changeset data from Git or GitHub source code management systems.

Object Type: Code Commit Report object name: code_commit Description: Code commit or changeset data from Git or GitHub source code management systems.
Attribute	Display Name	Type	Description
pluginConfiguration	Plugin Configuration	`STRING`	Name of the plugin configuration if the data was populated through a plugin such as ECSCM-Git
pluginName	Plugin Name	`STRING`	Name of the plugin if the data was populated through a plugin. For example, ECSCM-Git
source	SCM Type	`STRING`	Name of the source control management system. For example, `Git` or `Perforce`
sourceUrl	Commit URL	`STRING`	URL to the changeset in the SCM repository
baseDrilldownUrl	BaseDrilldown Url	`STRING`	Base URL used to construct the full URL for drilling down from a widget into an external source control management system such as Git. For example, ` 'git://git.apache.org/zookeeper.git'`
commitDate	Commit Date	`DATETIME`	Date when the changeset was committed or checked into the source control system
scmUrl	SCM Server URL	`STRING`	URL to the SCM repository or the SCM server name. For example, `'git://git.apache.org/zookeeper.git'`
scmRepoBranch	SCM Repository Branch	`STRING`	Repository branch. This is specific to Git or Git-based SCMs. For example, `'master'`
commitId	Commit ID	`STRING`	Unique identifier for the changeset in the source control management system. For example, the SHA number in Git or the changelist number in Perforce
commitAuthor	Commit Author	`STRING`	Changeset author name
commitAuthorId	Commit Author ID	`STRING`	Unique identifier for the changeset author in the source control management system. For example, `top-dev@my-org.com`
commitMessage	Commit Message	`STRING`	Commit message provided with the commit or changeset
codeLinesAdded	Code Line Added	`NUMBER`	Number of code lines added in the commit or changeset
codeLinesUpdated	Code lines Updated	`NUMBER`	Number of code lines updated in the commit or changeset
codeLinesRemoved	Code Lines Removed	`NUMBER`	Number of code lines deleted in the commit or changeset
filesAdded	Files Added	`NUMBER`	Number of files added in the commit or changeset
filesUpdated	File Updated	`NUMBER`	Number of files updated in the commit or changeset
filesRemoved	Filed Removed	`NUMBER`	Number of files removed in the commit or changeset

Attribute

Display Name

Type

Description

pluginConfiguration

Plugin Configuration

STRING

Name of the plugin configuration if the data was populated through a plugin such as ECSCM-Git

pluginName

Plugin Name

STRING

Name of the plugin if the data was populated through a plugin. For example, ECSCM-Git

source

SCM Type

STRING

Name of the source control management system. For example, Git or Perforce

sourceUrl

Commit URL

STRING

URL to the changeset in the SCM repository

baseDrilldownUrl

BaseDrilldown Url

STRING

Base URL used to construct the full URL for drilling down from a widget into an external source control management system such as Git. For example, ` 'git://git.apache.org/zookeeper.git'`

commitDate

Commit Date

DATETIME

Date when the changeset was committed or checked into the source control system

scmUrl

SCM Server URL

STRING

URL to the SCM repository or the SCM server name. For example, 'git://git.apache.org/zookeeper.git'

scmRepoBranch

SCM Repository Branch

STRING

Repository branch. This is specific to Git or Git-based SCMs. For example, 'master'

commitId

Commit ID

STRING

Unique identifier for the changeset in the source control management system. For example, the SHA number in Git or the changelist number in Perforce

commitAuthor

Commit Author

STRING

Changeset author name

commitAuthorId

Commit Author ID

STRING

Unique identifier for the changeset author in the source control management system. For example, top-dev@my-org.com

commitMessage

Commit Message

STRING

Commit message provided with the commit or changeset

codeLinesAdded

Code Line Added

NUMBER

Number of code lines added in the commit or changeset

codeLinesUpdated

Code lines Updated

NUMBER

Number of code lines updated in the commit or changeset

codeLinesRemoved

Code Lines Removed

NUMBER

Number of code lines deleted in the commit or changeset

filesAdded

Files Added

NUMBER

Number of files added in the commit or changeset

filesUpdated

File Updated

NUMBER

Number of files updated in the commit or changeset

filesRemoved

Filed Removed

NUMBER

Number of files removed in the commit or changeset

Defect

Object Type: Defect Report object name: defect Description: Defects logged in the Atlassian JIRA defect tracking system.

Object Type: Defect Report object name: defect Description: Defects logged in the Atlassian JIRA defect tracking system.
Attribute	Display Name	Type	Description
baseDrilldownUrl	Base Drilldown Url	`STRING`	Base URL used to construct the full URL for drilling down from a widget into a defect-tracking system such as Atlassian JIRA. For example, `https://jira101.myco.com?jql=project%3DTEST%20AND%20issuetype%3DBug`
createdOn	Created On	`DATETIME`	Date and time that the defect was created. The format is ISO 8601 in UTC time. For example, `2017-01-01T11:54:58.569Z`
defectName	Defect Name	`STRING`	Name of the defect
key	Unique Defect ID	`STRING`	Unique identifier for the defect in the defect tracking system
modifiedOn	Modified On	`DATETIME`	Date and time that the defect was last modified. The format is ISO 8601 in UTC time. For example, `2017-01-01T11:54:58.569Z`
pluginConfiguration	Plugin Configuration	`STRING`	Name of the plugin configuration if the data was populated through EC-JIRA
pluginName	Plugin Name	`STRING`	Name of the plugin if the data was populated through EC-JIRA. For example, `EC-JIRA`
releaseName	Release Name	`STRING`	Name of the release containing the defect
releaseProjectName	Release Project Name	`STRING`	Name of the project containing the defect
releaseUri	Release URI	`STRING`	Partial URL that can be used along with `baseDrilldownUrl` to construct the drill-down URL to navigate to the defects associated with the current release in the project management system. For example, for JIRA, if `baseDrilldownUrl` is set to `https://jira101.myco.com?jql=project%3DTEST%20AND%20issuetype%3DBug`, and the defects associated with the current release are assigned `fixVersion` value `7.5`, then the release URI can be set as `fixVersion=7.5` to then construct the external URL in the widget definition as `${baseDrilldownUrl}%20AND%20${releaseUri}`. This is expanded when the widget is rendered in the UI to `https://jira101.myco.com?jql=project%3DTEST%20AND%20issuetype%3DBug%20AND%20fixVersion=7.5` as a drill-down link
resolution	Resolution	`STRING`	Current resolution of the defect. The possible values depend on the defect tracking system
resolvedOn	Resolved On	`DATETIME`	Date and time that the defect was resolved. The format is ISO 8601 in UTC time. For example, `2017-01-01T11:54:58.569Z`
source	Source	`STRING`	Name of the defect tracking system. For example, `JIRA`
sourceUrl	Source Url	`STRING`	URL for the defect record. For example, `https://jira101.myco.com?jql=project%3DTEST%20AND%20issuetype%3DBug`
status	Status	`STRING`	Current status of the defect: `Open`, `Inprogress`, `Resolved`, or `Closed`
timestamp	Timestamp	`DATETIME`	Date and time when the defect record was last updated. The system uses this field to determine the time-based index for storing the defect records by year. For example, defects updated in 2017 are stored in the index `ef-defect-2017`. The format is ISO 8601 in UTC time. For example, `2017-01-01T11:54:58.569Z`
type	Type	`STRING`	Defect type. The possible values depend on the defect tracking system. The possible value for JIRA is `Bug`.

Attribute

Display Name

Type

Description

baseDrilldownUrl

Base Drilldown Url

STRING

Base URL used to construct the full URL for drilling down from a widget into a defect-tracking system such as Atlassian JIRA. For example, https://jira101.myco.com?jql=project%3DTEST%20AND%20issuetype%3DBug

createdOn

Created On

DATETIME

Date and time that the defect was created. The format is ISO 8601 in UTC time. For example, 2017-01-01T11:54:58.569Z

defectName

Defect Name

STRING

Name of the defect

key

Unique Defect ID

STRING

Unique identifier for the defect in the defect tracking system

modifiedOn

Modified On

DATETIME

Date and time that the defect was last modified. The format is ISO 8601 in UTC time. For example, 2017-01-01T11:54:58.569Z

pluginConfiguration

Plugin Configuration

STRING

Name of the plugin configuration if the data was populated through EC-JIRA

pluginName

Plugin Name

STRING

Name of the plugin if the data was populated through EC-JIRA. For example, EC-JIRA

releaseName

Release Name

STRING

Name of the release containing the defect

releaseProjectName

Release Project Name

STRING

Name of the project containing the defect

releaseUri

Release URI

STRING

Partial URL that can be used along with baseDrilldownUrl to construct the drill-down URL to navigate to the defects associated with the current release in the project management system.

For example, for JIRA, if baseDrilldownUrl is set to https://jira101.myco.com?jql=project%3DTEST%20AND%20issuetype%3DBug, and the defects associated with the current release are assigned fixVersion value 7.5, then the release URI can be set as fixVersion=7.5 to then construct the external URL in the widget definition as ${baseDrilldownUrl}%20AND%20${releaseUri}. This is expanded when the widget is rendered in the UI to https://jira101.myco.com?jql=project%3DTEST%20AND%20issuetype%3DBug%20AND%20fixVersion=7.5 as a drill-down link

resolution

Resolution

STRING

Current resolution of the defect. The possible values depend on the defect tracking system

resolvedOn

Resolved On

DATETIME

Date and time that the defect was resolved. The format is ISO 8601 in UTC time. For example, 2017-01-01T11:54:58.569Z

source

Source

STRING

Name of the defect tracking system. For example, JIRA

sourceUrl

Source Url

STRING

URL for the defect record. For example, https://jira101.myco.com?jql=project%3DTEST%20AND%20issuetype%3DBug

status

Status

STRING

Current status of the defect: Open, Inprogress, Resolved, or Closed

timestamp

Timestamp

DATETIME

Date and time when the defect record was last updated. The system uses this field to determine the time-based index for storing the defect records by year. For example, defects updated in 2017 are stored in the index ef-defect-2017.

The format is ISO 8601 in UTC time. For example, 2017-01-01T11:54:58.569Z

type

Type

STRING

Defect type. The possible values depend on the defect tracking system. The possible value for JIRA is Bug.

Deployment

Object Type: Deployment Report object name: deployment Description: Data from CloudBees CD application or microservice deployments.

Object Type: Deployment Report object name: deployment Description: Data from CloudBees CD application or microservice deployments.
Attribute	Display Name	Type	Description
applicationId	Application ID	`STRING`	Unique ID of the application that was deployed
applicationName	Application Name	`STRING`	Name of the application
approvedBy	Approved By	`STRING`	User who approved the manual step
clusterName	Cluster Name	`STRING`	Name of the cluster to which the service was deployed
comment	Comment	`STRING`	Comment provided when the user completed the manual step
deploymentOutcome	Deployment Outcome	`STRING`	Outcome of the deployment: `Success`, `Error`, `Warning`, or `Skipped` (check the job outcome)
elapsedTime	Elapsed Time	`STRING`	Time taken by the deployment to complete (in milliseconds)
environmentId	Environment ID	`STRING`	Unique ID of the environment to which the application or service was deployed
environmentName	Environment Name	`STRING`	Name of the environment
environmentProjectName	Environment Project Name	`STRING`	Name of the environment project
flowRuntimeId	CloudBees CD Runtime ID	`STRING`	ID of the pipeline run that started or triggered the deployment
flowRuntimeName	CloudBees CD Runtime Name	`STRING`	Name of the pipeline run that started deployment
flowRuntimeStateName	CloudBees CD Runtime State Name	`STRING`	Name of the stage or task that started the deployment
groupName	Group Name	`STRING`	Name of the group containing the task
jobAbortStatus	Job Abort Status	`STRING`	Abort status if the job was aborted: `ABORT` or `FORCEABORT`
jobAbortedBy	Job Aborted By	`STRING`	User who aborted the job
jobFinish	Job Finish	`DATETIME`	Job completion time
jobId	Job ID	`STRING`	Unique job ID
jobName	Job Name	`STRING`	Name of the job
jobOutcome	Job Outcome	`STRING`	Outcome of the job: `Success`, `Error`, `Warning`, or `Skipped`
jobStart	Job Start	`DATETIME`	Job start time
jobStatus	Job Status	`STRING`	Status of the job: `pending`, `runnable`, `running`, or `scheduled`
jobStepAbortStatus	Job Step Abort Status	`STRING`	Abort status of the job step: `ABORT` or `FORCE_ABORT`
jobStepAbortedBy	Job Step Aborted By	`STRING`	User or project that aborted the job step
jobStepName	Job Step Name	`STRING`	Name of the job step
jobStepOutcome	Job Step Outcome	`STRING`	Outcome of the job step: `Success`, `Error`, `Warning`, or `Skipped`
jobStepStatus	Job Step Status	`STRING`	Status of the job step: `Pending`, `Runnable`, `Scheduled`, `Running`, or `Completed`
jobStepType	Job Step Type	`STRING`	Type of the job step
jobType	Job Type	`STRING`	Type of the job: `rollback` (set only for rollback jobs)
launchedByUser	Launched By User	`STRING`	User who launched the job
manual	Manual	`BOOLEAN`	Boolean flag to indicate if a step is manual
parentTaskId	Parent Task ID	`STRING`	Id of parent task.
parentTaskName	Parent Task Name	`STRING`	Name of the parent task
parentTaskType	Parent Task Type	`STRING`	Task type of the parent task
pipelineId	Pipeline ID	`STRING`	ID of the pipeline containing the task that launched the job
pipelineName	Pipeline Name	`STRING`	Name of the pipeline containing the task that launched the job
pipelineRunOutcome	Pipeline Run Outcome	`STRING`	Outcome of the pipeline run: `Success`, `Error`, `Warning`, `Skipped`, or `Aborted`
plannedEndTime	Planned End Time	`DATETIME`	Planned end date of the task that triggered the deployment.
plannedStartTime	Planned Start Time	`DATETIME`	Planned start date of the task that triggered the deployment.
pluginDisplayName	Plugin Display Name	`STRING`	Display name of the plugin
pluginKey	Plugin Key	`STRING`	Key of the plugin
processId	Process ID	`STRING`	ID of the process that launched the job
processName	Process Name	`STRING`	Name of the process that launched the job
processStepName	Process Step Name	`STRING`	Name of the process step in the process
projectId	Project ID	`STRING`	ID of the project
projectName	Project Name	`STRING`	Name of the project
releaseId	Release ID	`STRING`	ID of the release to which the pipeline runs belongs
releaseName	Release Name	`STRING`	Name of the release to which the pipeline run belongs
releaseProjectName	Release Project Name	`STRING`	Name of the project containing the release
reportEventType	Report Event Type	`STRING`	Type of report event: ef_pipeline_run_completed ef_pipeline_run_gate_completed ef_pipeline_run_gate_started ef_pipeline_run_stage_completed ef_pipeline_run_stage_started ef_pipeline_run_started ef_pipeline_run_task_completed ef_pipeline_run_task_started ef_process_run_completed ef_process_run_rollback_step_completed ef_process_run_rollback_step_started ef_process_run_started ef_process_run_step_retry_completed ef_process_run_step_retry_started ef_process_run_waiting_on_manual ef_process_run_waiting_on_manual_completed
retries	Retries	`NUMBER`	Number of times to retry a step upon an error
retryType	Retry Type	`STRING`	Type of retry: `auto` or `manual`
serviceId	Service ID	`STRING`	ID of the service associated with the job
serviceName	Service Name	`STRING`	Name of the service associated with the job
stageName	Stage Name	`STRING`	Name of the stage containing the task that launched the job
taskName	Task Name	`STRING`	Name of the task that launched the job
taskStatus	Task Status	`STRING`	Status of the task
taskType	Taks Type	`STRING`	Type of the task: `APPROVAL COMMAND CONDITIONAL DEPLOYER GROUP MANUAL PIPELINE PLUGIN PROCEDURE PROCESS RELEASE UTILITY WORKFLOW`
tierMapName	Tier Map Name	`STRING`	Name of the tier map
waitForPlannedStart	Wait For Planned Start	`BOOLEAN`	Boolean flag that represents whether a task should wait for a planned start date before running.

Attribute

Display Name

Type

Description

applicationId

Application ID

STRING

Unique ID of the application that was deployed

applicationName

Application Name

STRING

Name of the application

approvedBy

Approved By

STRING

User who approved the manual step

clusterName

Cluster Name

STRING

Name of the cluster to which the service was deployed

comment

Comment

STRING

Comment provided when the user completed the manual step

deploymentOutcome

Deployment Outcome

STRING

Outcome of the deployment: Success, Error, Warning, or Skipped (check the job outcome)

elapsedTime

Elapsed Time

STRING

Time taken by the deployment to complete (in milliseconds)

environmentId

Environment ID

STRING

Unique ID of the environment to which the application or service was deployed

environmentName

Environment Name

STRING

Name of the environment

environmentProjectName

Environment Project Name

STRING

Name of the environment project

flowRuntimeId

CloudBees CD Runtime ID

STRING

ID of the pipeline run that started or triggered the deployment

flowRuntimeName

CloudBees CD Runtime Name

STRING

Name of the pipeline run that started deployment

flowRuntimeStateName

CloudBees CD Runtime State Name

STRING

Name of the stage or task that started the deployment

groupName

Group Name

STRING

Name of the group containing the task

jobAbortStatus

Job Abort Status

STRING

Abort status if the job was aborted: ABORT or FORCEABORT

jobAbortedBy

Job Aborted By

STRING

User who aborted the job

jobFinish

Job Finish

DATETIME

Job completion time

jobId

Job ID

STRING

Unique job ID

jobName

Job Name

STRING

Name of the job

jobOutcome

Job Outcome

STRING

Outcome of the job: Success, Error, Warning, or Skipped

jobStart

Job Start

DATETIME

Job start time

jobStatus

Job Status

STRING

Status of the job: pending, runnable, running, or scheduled

jobStepAbortStatus

Job Step Abort Status

STRING

Abort status of the job step: ABORT or FORCE_ABORT

jobStepAbortedBy

Job Step Aborted By

STRING

User or project that aborted the job step

jobStepName

Job Step Name

STRING

Name of the job step

jobStepOutcome

Job Step Outcome

STRING

Outcome of the job step: Success, Error, Warning, or Skipped

jobStepStatus

Job Step Status

STRING

Status of the job step: Pending, Runnable, Scheduled, Running, or Completed

jobStepType

Job Step Type

STRING

Type of the job step

jobType

Job Type

STRING

Type of the job: rollback (set only for rollback jobs)

launchedByUser

Launched By User

STRING

User who launched the job

manual

Manual

BOOLEAN

Boolean flag to indicate if a step is manual

parentTaskId

Parent Task ID

STRING

Id of parent task.

parentTaskName

Parent Task Name

STRING

Name of the parent task

parentTaskType

Parent Task Type

STRING

Task type of the parent task

pipelineId

Pipeline ID

STRING

ID of the pipeline containing the task that launched the job

pipelineName

Pipeline Name

STRING

Name of the pipeline containing the task that launched the job

pipelineRunOutcome

Pipeline Run Outcome

STRING

Outcome of the pipeline run: Success, Error, Warning, Skipped, or Aborted

plannedEndTime

Planned End Time

DATETIME

Planned end date of the task that triggered the deployment.

plannedStartTime

Planned Start Time

DATETIME

Planned start date of the task that triggered the deployment.

pluginDisplayName

Plugin Display Name

STRING

Display name of the plugin

pluginKey

Plugin Key

STRING

Key of the plugin

processId

Process ID

STRING

ID of the process that launched the job

processName

Process Name

STRING

Name of the process that launched the job

processStepName

Process Step Name

STRING

Name of the process step in the process

projectId

Project ID

STRING

ID of the project

projectName

Project Name

STRING

Name of the project

releaseId

Release ID

STRING

ID of the release to which the pipeline runs belongs

releaseName

Release Name

STRING

Name of the release to which the pipeline run belongs

releaseProjectName

Release Project Name

STRING

Name of the project containing the release

reportEventType

Report Event Type

STRING

Type of report event:

ef_pipeline_run_completed

ef_pipeline_run_gate_completed

ef_pipeline_run_gate_started

ef_pipeline_run_stage_completed

ef_pipeline_run_stage_started

ef_pipeline_run_started

ef_pipeline_run_task_completed

ef_pipeline_run_task_started

ef_process_run_completed

ef_process_run_rollback_step_completed

ef_process_run_rollback_step_started

ef_process_run_started

ef_process_run_step_retry_completed

ef_process_run_step_retry_started

ef_process_run_waiting_on_manual

ef_process_run_waiting_on_manual_completed

retries

Retries

NUMBER

Number of times to retry a step upon an error

retryType

Retry Type

STRING

Type of retry: auto or manual

serviceId

Service ID

STRING

ID of the service associated with the job

serviceName

Service Name

STRING

Name of the service associated with the job

stageName

Stage Name

STRING

Name of the stage containing the task that launched the job

taskName

Task Name

STRING

Name of the task that launched the job

taskStatus

Task Status

STRING

Status of the task

taskType

Taks Type

STRING

Type of the task:

APPROVAL

COMMAND

CONDITIONAL

DEPLOYER

GROUP

MANUAL

PIPELINE

PLUGIN

PROCEDURE

PROCESS

RELEASE

UTILITY

WORKFLOW

tierMapName

Tier Map Name

STRING

Name of the tier map

waitForPlannedStart

Wait For Planned Start

BOOLEAN

Boolean flag that represents whether a task should wait for a planned start date before running.

Feature

Object Type: Feature Report object name: feature Description: Features or stories tracked in the Atlassian JIRA project management tool.

Object Type: Feature Report object name: feature Description: Features or stories tracked in the Atlassian JIRA project management tool.
Attribute	Display Name	Type	Description
baseDrilldownUrl	Base Drilldown Url	`STRING`	Base URL used to construct the full URL for drilling down from a widget into a system such as JIRA. For example, `https://jira101.myco.com?jql=project%3DTEST%20AND%20issuetype%3DStory`
createdOn	Created On	`DATETIME`	Date and time that the feature was created. The format is ISO 8601 in UTC time. For example, `2017-01-01T11:54:58.569Z `
featureName	Feature Name	`STRING`	Name of the feature
featuretype	Feature Type	`STRING`	Type of the feature : `Improvement`, `New Feature`, or `Story`
key	Unique Feature ID	`STRING`	Unique identifier for the feature in the project management tool
modifiedOn	Modified On	`DATETIME`	Date and time that the feature was last modified. The format is ISO 8601 in UTC time. For example, `2017-01-01T11:54:58.569Z`
pluginConfiguration	Plugin Configuration	`STRING`	Name of the plugin configuration if the data was populated through EC-JIRA
pluginName	Plugin Name	`STRING`	Name of the plugin if the data was populated through EC-JIRA. For example, `EC-JIRA`
releaseName	Release Name	`STRING`	Name of the release containing the feature
releaseProjectName	Release Project Name	`STRING`	Name of the project containing the feature
releaseUri	Release URI	`STRING`	Partial URL that can be used along with `baseDrilldownUrl` to construct the drill-down URL to navigate to the features associated with the current release in the project management system. For example, for JIRA, if `baseDrilldownUrl` was set to `https://jira101.myco.com?jql=project%3DTEST%20AND%20issuetype%3DStory`, and if the features associated with the current release were assigned fixVersion value `7.5`, then `releaseUri` can be set as `fixVersion=7.5` to then construct the external URL in the widget definition as `${baseDrilldownUrl}%20AND%20${releaseUri}`. This is expanded when the widget is rendered in the UI to `https://jira101.myco.com?jql=project%3DTEST%20AND%20issuetype%3DStory%20AND%20fixVersion=7.5` as a drill-down link
resolution	Resolution	`STRING`	Current resolution of the feature. Possible values include: `Fixed`, `Duplicate`, `Won’t Fix`, `Incomplete`, or `Cannot Reproduce`.
resolvedOn	Resolved On	`DATETIME`	Date and time that the feature was resolved. The format is ISO 8601 in UTC time. For example, `2017-01-01T11:54:58.569Z`
source	Source	`STRING`	Name of the project management tool. For example, `JIRA`
sourceUrl	Source Url	`STRING`	URL for the feature record. For example, `https://jira101.myco.com/browse/ARR-18001`
status	Status	`STRING`	Current status of the feature: `Open`, `Inprogress`, Resolved ` or `Closed
storyPoints	Story Points	`NUMBER`	Number of story points assigned to the feature. This can be any integer
tags	Tags	`STRING`	Tags or labels associated with the feature.
timestamp	Timestamp	`DATETIME`	Date and time that the feature record was last updated. The system uses this field to determine the time-based index for storing the feature records by year. For example, features updated in 2017 are stored in the index `ef-feature-2017`. The format is ISO 8601 in UTC time. For example, `2017-01-01T11:54:58.569Z`

Attribute

Display Name

Type

Description

baseDrilldownUrl

Base Drilldown Url

STRING

Base URL used to construct the full URL for drilling down from a widget into a system such as JIRA. For example, https://jira101.myco.com?jql=project%3DTEST%20AND%20issuetype%3DStory

createdOn

Created On

DATETIME

Date and time that the feature was created. The format is ISO 8601 in UTC time. For example, `2017-01-01T11:54:58.569Z `

featureName

Feature Name

STRING

Name of the feature

featuretype

Feature Type

STRING

Type of the feature : Improvement, New Feature, or Story

key

Unique Feature ID

STRING

Unique identifier for the feature in the project management tool

modifiedOn

Modified On

DATETIME

Date and time that the feature was last modified. The format is ISO 8601 in UTC time. For example, 2017-01-01T11:54:58.569Z

pluginConfiguration

Plugin Configuration

STRING

Name of the plugin configuration if the data was populated through EC-JIRA

pluginName

Plugin Name

STRING

Name of the plugin if the data was populated through EC-JIRA. For example, EC-JIRA

releaseName

Release Name

STRING

Name of the release containing the feature

releaseProjectName

Release Project Name

STRING

Name of the project containing the feature

releaseUri

Release URI

STRING

Partial URL that can be used along with baseDrilldownUrl to construct the drill-down URL to navigate to the features associated with the current release in the project management system. For example, for JIRA, if baseDrilldownUrl was set to https://jira101.myco.com?jql=project%3DTEST%20AND%20issuetype%3DStory, and if the features associated with the current release were assigned fixVersion value 7.5, then releaseUri can be set as fixVersion=7.5 to then construct the external URL in the widget definition as ${baseDrilldownUrl}%20AND%20${releaseUri}. This is expanded when the widget is rendered in the UI to https://jira101.myco.com?jql=project%3DTEST%20AND%20issuetype%3DStory%20AND%20fixVersion=7.5 as a drill-down link

resolution

Resolution

STRING

Current resolution of the feature. Possible values include: Fixed, Duplicate, Won’t Fix, Incomplete, or Cannot Reproduce.

resolvedOn

Resolved On

DATETIME

Date and time that the feature was resolved. The format is ISO 8601 in UTC time. For example, 2017-01-01T11:54:58.569Z

source

Source

STRING

Name of the project management tool. For example, JIRA

sourceUrl

Source Url

STRING

URL for the feature record. For example, https://jira101.myco.com/browse/ARR-18001

status

Status

STRING

Current status of the feature: Open, Inprogress, Resolved ` or `Closed

storyPoints

Story Points

NUMBER

Number of story points assigned to the feature. This can be any integer

tags

Tags

STRING

Tags or labels associated with the feature.

timestamp

Timestamp

DATETIME

Date and time that the feature record was last updated. The system uses this field to determine the time-based index for storing the feature records by year. For example, features updated in 2017 are stored in the index ef-feature-2017.

The format is ISO 8601 in UTC time. For example, 2017-01-01T11:54:58.569Z

Incident

Object Type: Incident Report object name: incident Description: Incidents logged and managed in the ServiceNow ITSM system for post-production deployed releases.

Object Type: Incident Report object name: incident Description: Incidents logged and managed in the ServiceNow ITSM system for post-production deployed releases.
Attribute	Display Name	Type	Description
baseDrilldownUrl	Base Drilldown Url	`STRING`	Base URL used to construct the full URL for drilling down from a widget into a system such as ServiceNow. For example, `https://ven02149.service-now.com/incident_list.do?sysparm_query=^{incident_state=6}ORincident_state=7`
category	Category	`STRING`	Category containing the incident. The possible values depend on the ITSM system
configurationItem	Configuration Item	`STRING`	Configuration item name for the incident in the ITSM system
createdOn	Created On	`DATETIME`	Date and time that the incident was created. The format is ISO 8601 in UTC time. For example, `2017-01-01T11:54:58.569Z `
incidentId	Unique Incident ID	`STRING`	Unique ID of the incident
modifiedOn	Modified On	`DATETIME`	Date and time that the incident was last modified. The format is ISO 8601 in UTC time. For example, `2017-01-01T11:54:58.569Z`
pluginConfiguration	Plugin Configuration	`STRING`	Name of the plugin configuration if the data was populated through EC-ServiceNow
pluginName	Plugin Name	`STRING`	Name of the plugin if the data was populated through EC-ServiceNow. For example, `EC-ServiceNow`
priority	Priority	`STRING`	Incident priority. The possible values depend on the ITSM system
releaseName	Release Name	`STRING`	Name of the release for which the incident occurred
releaseProjectName	Release Project Name	`STRING`	Name of the project containing the release for which the incident occurred
releaseUri	Release URI	`STRING`	Partial URL that can be used along with `baseDrilldownUrl` to construct the drill-down URL to navigate to the incidents associated with the current release in the ITSM system. For example, for ServiceNow, if `baseDrilldownUrl` is set to show all resolved or closed incidents: `https://ven02149.service-now.com/incident_list.do?sysparm_query=^{incident_state=6}ORincident_state=7`, and if the incidents associated with the current release belonged to the online-portal category, then the release URL can be set as `category=software` to construct the external URL in the widget definition as `${baseDrilldownUrl}^${releaseUri}`. This is expanded when the widget is rendered in the UI to `https://ven01735.service-now.com/incident_list.do?sysparm_query=^{incident_state=6}ORincident_state=7^category=software` as a drill-down link
reportedBy	Reported By	`STRING`	User name of the reporter of the incident
resolvedOn	Resolved On	`DATETIME`	Date and time that the incident was resolved. The format is ISO 8601 in UTC time. For example, `2017-01-01T11:54:58.569Z`
source	Source	`STRING`	Name of the ITSM system. For example, `ServiceNow`
sourceUrl	Source URL	`STRING`	URL for the incident record in the source system. For example, `https://ven02149.service-now.com/nav_to.do?uri=incident.do?sys_id=46ee0924a9fe198100f1cf78c198454a`
status	Status	`STRING`	Current status of the incident. Possible values include `New`, `Active`, `Resolved`, or `Closed`. The actual values depend on the ITSM system
subCategory	Sob Category	`STRING`	Subcategory containing the incident. The possible values depend on the ITSM system
timestamp	Timestamp	`DATETIME`	Date and time when the incident was last updated. The system uses this field to determine the time-based index for storing the incident records by year. For example, updated in 2017 are stored in the index `ef-incident-2017`. The format is ISO 8601 in UTC time. For example, `2017-01-01T11:54:58.569Z`

Attribute

Display Name

Type

Description

baseDrilldownUrl

Base Drilldown Url

STRING

Base URL used to construct the full URL for drilling down from a widget into a system such as ServiceNow. For example, https://ven02149.service-now.com/incident_list.do?sysparm_query=^{incident_state=6}ORincident_state=7

Job

Object Type: CloudBees CD Job Report object name: job Description: Data from CloudBees CD jobs (the output associated with invoking a CloudBees CD procedure or process)

Object Type: CloudBees CD Job Report object name: job Description: Data from CloudBees CD jobs (the output associated with invoking a CloudBees CD procedure or process)
Attribute	Display Name	Type	Description
applicationId	Application ID	`STRING`	Unique ID of the application process for which the job was run
applicationName	Application Name	`STRING`	Name of the application
elapsedTime	Elapsed Time	`STRING`	Time taken by the job to complete (in milliseconds)
environmentId	Environment ID	`STRING`	Unique ID of the environment to which the application or service was deployed
environmentName	Environment Name	`STRING`	Name of the environment
environmentProjectName	Environment Project Name	`STRING`	Name of the environment project
flowRuntimeId	Pipeline Run ID	`STRING`	ID of the pipeline run that started or triggered the job
jobFinish	End Time	`DATETIME`	Job completion time
jobID	Job ID	STRING	Unique job ID
jobName	Job Name	`STRING`	Name of the job
jobStart	Start Time	`DATETIME`	Job start time
combinedStatus	Job Result	`STRING`	Set using `combinedStatus`. Job details are sent for completed jobs only, so possible values based on terminal combined status are `Aborted`, `Error`, `Success`, `Warning`, or `Skipped`
launchedByUser	Launched By User	`STRING`	User who launched the job
pipelineId	Pipeline ID	`STRING`	ID of the pipeline containing the task that launched the job
projectName	Project Name	`STRING`	Name of the project
releaseId	Release ID	`STRING`	ID of the release to which the pipeline runs belongs
releaseName	Release Name	`STRING`	Name of the release to which the pipeline run belongs
releaseProjectName	Release Project Name	`STRING`	Name of the project containing the release
serviceId	Service ID	`STRING`	ID of the service associated with the job
serviceName	Service Name	`STRING`	Name of the service associated with the job
tags	Tags	`STRING`	Tags associated with the job

Attribute

Display Name

Type

Description

applicationId

Application ID

STRING

Unique ID of the application process for which the job was run

applicationName

Application Name

STRING

Name of the application

elapsedTime

Elapsed Time

STRING

Time taken by the job to complete (in milliseconds)

environmentId

Environment ID

STRING

Unique ID of the environment to which the application or service was deployed

environmentName

Environment Name

STRING

Name of the environment

environmentProjectName

Environment Project Name

STRING

Name of the environment project

flowRuntimeId

Pipeline Run ID

STRING

ID of the pipeline run that started or triggered the job

jobFinish

End Time

DATETIME

Job completion time

jobID

Job ID

STRING

Unique job ID

jobName

Job Name

STRING

Name of the job

jobStart

Start Time

DATETIME

Job start time

combinedStatus

Job Result

STRING

Set using combinedStatus. Job details are sent for completed jobs only, so possible values based on terminal combined status are Aborted, Error, Success, Warning, or Skipped

launchedByUser

Launched By User

STRING

User who launched the job

pipelineId

Pipeline ID

STRING

ID of the pipeline containing the task that launched the job

projectName

Project Name

STRING

Name of the project

releaseId

Release ID

STRING

ID of the release to which the pipeline runs belongs

releaseName

Release Name

STRING

Name of the release to which the pipeline run belongs

releaseProjectName

Release Project Name

STRING

Name of the project containing the release

serviceId

Service ID

STRING

ID of the service associated with the job

serviceName

Service Name

STRING

Name of the service associated with the job

tags

Tags

STRING

Tags associated with the job

Pipeline Run

Object Type: Pipeline Run Report object name: pipelinerun Description: Data from pipeline runs in CloudBees CD such as pipeline run outcome and runtime start and end times

Object Type: Pipeline Run Report object name: pipelinerun Description: Data from pipeline runs in CloudBees CD such as pipeline run outcome and runtime start and end times
Attribute	Display Name	Type	Description
action	Manual task/step action	`STRING`	Action the user took to complete the manual task or step: `completed` or `failed`
applicationName	Application Name	`STRING`	Name of the application
applicationProjectName	Application Project Name	`STRING`	Name of the project containing the application
approvedBy	Approved By	`STRING`	Name of the user who approved the stage or gate task
approvers	Approvers	`STRING`	List of approvers for the stage or gate task
elapsedTime	Elapsed Time	`STRING`	Time taken by the pipeline run to complete (in milliseconds)
evidence	Evidence	`STRING`	Evidence that the task was run
flowRuntimeAbortStatus	Pipeline Run Abort Status	`STRING`	Abort status of the pipeline run if it was aborted: `ABORT` or `FORCEABORT`
flowRuntimeAbortedBy	Pipeline Run Aborted By	`STRING`	User who aborted the pipeline run
flowRuntimeCompleted	Pipeline Run Completed	`BOOLEAN`	Boolean flag to indicate if the pipeline run is completed
flowRuntimeFinish	Pipeline Run Finish Time	`DATETIME`	Time when the pipeline run was completed
flowRuntimeId	Pipeline Run ID	`STRING`	ID of the pipeline run
flowRuntimeName	CloudBees CD Runtime Name	`STRING`	Name of the pipeline run
flowRuntimeStart	Pipeline Run Start Time	`DATETIME`	Time when the pipeline run started
flowRuntimeStateAbortStatus	Task/Stage Run abort status	`STRING`	Abort status of a stage, task, or gate associated with the pipeline run: `ABORT` or `FORCEABORT`
flowRuntimeStateAbortedBy	Task/Stage Run aborted by	`STRING`	User who aborted the stage, task, or gate in the pipeline run
flowRuntimeStateFinish	Task/Stage Run finish time	`DATETIME`	Time when the stage, task, or gate finished execution in the pipeline run
flowRuntimeStateId	Task/Stage Run ID	`STRING`	ID of the runtime object associated with the stage, task, or gate in the pipeline run
flowRuntimeStateName	CloudBees CD Runtime State Name	`STRING`	Name of the runtime object associated with the stage, task, or gate in the pipeline run
flowRuntimeStateOutcome	CloudBees CD Runtime State Outcome	`STRING`	Outcome of execution of the runtime object associated with the stage, task, or gate in the pipeline run: `Success`, `Error`, `Warning`, or `Skipped`
flowRuntimeStateStart	Task/Stage Run start time	`DATETIME`	Time when the stage, task, or gate started execution in the pipeline run
gateType	Gate Type	`STRING`	Type of gate: `PRE` or `POST`
groupName	Group Name	`STRING`	Name of the group task
manual	Manual	`BOOLEAN`	Boolean flag to indicate if it is a manual or an approval task
parentTaskId	Parent Task ID	`STRING`	Id of parent task.
parentTaskName	Parent Task Name	`STRING`	Name of the parent task (either a deployer task or a group task)
parentTaskType	Parent Task Type	`STRING`	Type of the parent task
pipelineId	Pipeline ID	`STRING`

Attribute

Display Name

Type

Description

action

Manual task/step action

STRING

Action the user took to complete the manual task or step: completed or failed

applicationName

Application Name

STRING

Name of the application

applicationProjectName

Application Project Name

STRING

Name of the project containing the application

approvedBy

Approved By

STRING

Name of the user who approved the stage or gate task

approvers

Approvers

STRING

List of approvers for the stage or gate task

elapsedTime

Elapsed Time

STRING

Time taken by the pipeline run to complete (in milliseconds)

evidence

Evidence

STRING

Evidence that the task was run

flowRuntimeAbortStatus

Pipeline Run Abort Status

STRING

Abort status of the pipeline run if it was aborted: ABORT or FORCEABORT

flowRuntimeAbortedBy

Pipeline Run Aborted By

STRING

User who aborted the pipeline run

flowRuntimeCompleted

Pipeline Run Completed

BOOLEAN

Boolean flag to indicate if the pipeline run is completed

flowRuntimeFinish

Pipeline Run Finish Time

DATETIME

Time when the pipeline run was completed

flowRuntimeId

Pipeline Run ID

STRING

ID of the pipeline run

flowRuntimeName

CloudBees CD Runtime Name

STRING

Name of the pipeline run

flowRuntimeStart

Pipeline Run Start Time

DATETIME

Time when the pipeline run started

flowRuntimeStateAbortStatus

Task/Stage Run abort status

STRING

Abort status of a stage, task, or gate associated with the pipeline run: ABORT or FORCEABORT

flowRuntimeStateAbortedBy

Task/Stage Run aborted by

STRING

User who aborted the stage, task, or gate in the pipeline run

flowRuntimeStateFinish

Task/Stage Run finish time

DATETIME

Time when the stage, task, or gate finished execution in the pipeline run

flowRuntimeStateId

Task/Stage Run ID

STRING

ID of the runtime object associated with the stage, task, or gate in the pipeline run

flowRuntimeStateName

CloudBees CD Runtime State Name

STRING

Name of the runtime object associated with the stage, task, or gate in the pipeline run

flowRuntimeStateOutcome

CloudBees CD Runtime State Outcome

STRING

Outcome of execution of the runtime object associated with the stage, task, or gate in the pipeline run: Success, Error, Warning, or Skipped

flowRuntimeStateStart

Task/Stage Run start time

DATETIME

Time when the stage, task, or gate started execution in the pipeline run

gateType

Gate Type

STRING

Type of gate: PRE or POST

groupName

Group Name

STRING

Name of the group task

manual

Manual

BOOLEAN

Boolean flag to indicate if it is a manual or an approval task

parentTaskId

Parent Task ID

STRING

Id of parent task.

parentTaskName

Parent Task Name

STRING

Name of the parent task (either a deployer task or a group task)

parentTaskType

Parent Task Type

STRING

Type of the parent task

pipelineId

Pipeline ID

STRING