Export CSV

Export pipeline data

Data structure

Field Name	Source	Description	Note
Pipeline Name	pipeline name	selected pipeline name on metrics page
Pipeline Step	pipeline step name	selected step name on metrics page
Build Number	buildInfo.number	obtain buildInfos based on the organization and pipeline name, and filter out the `passed/failed` buildInfo with the selected step name,you can retrieve the `buildInfo.number`
Committer	commitInfo.commit.committer.name	to obtain buildInfos and the repository of the pipeline based on the organization and pipeline name,and filter out the `passed/failed` buildInfo with the selected step name,can retrieve the `buildInfo.commit`.then obtain `commitInfo` according to the repository and commit	when selecting and configuring the leadTimeForChanges field on the config page, the field will be calculated
Code Committed Time	commitInfo.commit.committer.date	consistent with the above description	when selecting and configuring the leadTimeForChanges field on the config page, the field will be calculated
First Code Committed Time In PR	leadTimeInfo.firstCommitTimeInPr	obtain buildInfos and the repository of the pipeline according to the organization and pipeline name, then calculate leadTimes according to the selected step and repository, and finally generate leadTimeInfo according to leadTimes	when selecting and configuring the leadTimeForChanges field on the config page, the field will be calculated
PR Created Time	leadTimeInfo.prCreatedTime	consistent with the above description	when selecting and configuring the leadTimeForChanges field on the config page, the field will be calculated
PR Merged Time	leadTimeInfo.prMergedTime	consistent with the above description	when selecting and configuring the leadTimeForChanges field on the config page, the field will be calculated
PR lead time (HH:mm )	leadTimeInfo.prDelayTime	consistent with the above description	when selecting and configuring the leadTimeForChanges field on the config page, the field will be calculated
Total Lead Time (HH:mm )	leadTimeInfo.totalTime	consistent with the above description	old app: when leadTimeForChanges is not selected on the config page, but Deployment frequency/Change failure rate/MTTR is selected, a leadTimeInfo without mergeDelayTime can be generated according to buildInfo’s commit, pipelineCreateTime and deployInfo’s finishedTime, new app: when selecting and configuring the leadTimeForChanges field on the config page, the field will be calculated
Deployment Completed Time	leadTimeInfo.jobFinishTime	consistent with the above description	when leadTimeForChanges is not selected on the config page, but Deployment frequency/Change failure rate/MTTR is selected, a leadTimeInfo without mergeDelayTime can be generated according to buildInfo’s commit, pipelineCreateTime and deployInfo’s finishedTime
Pipeline lead time (HH:mm )	leadTimeInfo.pipelineDelayTime	consistent with the above description	consistent with the above description
Status	deployInfo.state	obtain the deployInfos of buildInfo according to the organization and pipeline name, then query the first deployInfo that meets the criteria of the selected step and state

Impact w/o metrics set up

On the config page, selecting Lead times for changes, Deployment frequency, Change failure rate, or Mean time to recovery will display the export pipeline data button.
Only selecting Lead times for changes, can get value of Committer,Code Committed Time and completed leadTimeInfo.
On the metrics page, selecting different pipeline and step will show different data.

Export board data

Data structure

Field Name	Source	Description	Note
Issue Key	CardCollection.jiraCardDTOList.baseInfo.key	the card ID
Summary	CardCollection.jiraCardDTOList.baseInfo.fields.summary	the specific description of this card
Issue Type	CardCollection.jiraCardDTOList.baseInfo.fields.issuetype	the card type (Tech, Bug, Story)
Status	CardCollection.jiraCardDTOList.baseInfo.fields.status	the card in status
Story Points	CardCollection.jiraCardDTOList.baseInfo.fields.storyPoints	the card story point estimate
Assignee	CardCollection.jiraCardDTOList.baseInfo.fields.assignee	the card belongs to which member
Reporter	CardCollection.jiraCardDTOList.baseInfo.fields.reporter	the team member who created this card
Project Key	CardCollection.jiraCardDTOList.baseInfo.fields.project.key	abbreviation of Project Key
Project Name	CardCollection.jiraCardDTOList.baseInfo.fields.project.name	(Auto Dora Metrics) Project Name
Priority	CardCollection.jiraCardDTOList.baseInfo.fields.priority	distinguish the degree of urgency of a card
Parent Summary	CardCollection.jiraCardDTOList.baseInfo.fields.parent	detail info for parent card link or issue key?? (but now: Tech Stack Replacement)
Sprint	CardCollection.jiraCardDTOList.baseInfo.fields.sprint	iteration number
Labels	CardCollection.jiraCardDTOList.baseInfo.fields.labels	cards label
CustomField	CardCollection.jiraCardDTOList.baseInfo.fields.customFields	all customFields
Cycle Time	CardCollection.jiraCardDTOList.cardCycleTime.total	All the time it takes for this card to done from the doing
Cycle Time / Story Points	CardCollection.jiraCardDTOList.cardCycleTime.total/CardCollection.jiraCardDTOList.baseInfo.fields.storyPoints	cycle time of this card per story point of day
Columns CycleTime	CardCollection.jiraCardDTOList.cycleTimeList	The time this card spent in each column
Columns OriginCycleTime	CardCollection.jiraCardDTOList.originCycleTimeList	consistent with the above description

Impact w/o metrics set up

On the config page, selecting Velocity, Cycle Time or Classicfation will display the export board data button.
Only selecting Classification, can get value of custom field.
On the metrics page, selecting Consider the "Flag" as "Block" will calculate Cycle Time, Take “Flag” cost time as “Block”.
On the metrics page, selecting different crews, boardSetting and classification will show different data.