Page Comparison

{
"JIRA":{
"uuid":"uuid",
"order":2,
"displayText":"Issues",
"category":"ALM",
"issueKey":"key",
"property":"categoryName",
"epicKey":"epicKey",
"issueType":"issueType",
"toolName":"toolName",
"creationDate":"creationDate",
"resolutionsdate":"resolutionsdate",
"issueStatus":"status",
"author":"reporter",
"projectName":"projectName",
"timestamp":"inSightsTime",
"priority":"priority",
"inSightsTimeX":"inSightsTimeX",
"eventKey":"eventKey",
"uptool":[
"EPIC"
],
"downtool":[
"GIT"
],
"messages":[
{
"Message":"Total {0} in JIRA",
"Operation":"PROPERTY_COUNT",
"OperandName":"issueType",
"OperandValue":[
]
}
],
"uifilter":[
"key"
],
"cardDisplayProps":[
"issueKey",
"author",
"issueStatus",
"issueType"
],
"excludeLabels":["SPRINT"]
},
"GIT":{
"uuid":"uuid",
"category":"SCM",
"order":3,
"displayText":"Commits",
"inSightsTimeX":"inSightsTimeX",
"commitId":"commitId",
"property":"categoryName",
"toolName":"toolName",
"commitStatus":"status",
"author":"authorName",
"repositoryName":"repoName",
"timestamp":"inSightsTime",
"jiraKey":"jiraKey",
"gitCommiTime":"gitCommitTime",
"uptool":[
"JIRA"
],
"downtool":[
"JENKINS"
] ,
"messages":[
{
"Message":"Total {0} Developers ",
"Operation":"DISTINCT_COUNT",
"OperandName":"author",
"OperandValue":[
]
}
],
"uifilter":[
"commitId"
],
"cardDisplayProps":[
"commitId",
"property",
"jiraKey",
"author"

],
"excludeLabels":["FILE_CHANGE"]
}
}

Traceability.json file is divided into three sections :

Pipeline Properties . (Mandatory Properties)

1. uuid : uuid of the neo4j node.

2. order : the order needs to be set to each tool in order to maintain sequence in pipeline view the order is integer value for ex( order:1,2,3....etc).

3. toolName:  toolname of the node .
4. issueType: type of issue (for ALM tools).
5. epicKey: epic key (for ALM tools).
6. toolstatus : toolstatus of the node.
7. property: category name in neo4j.
8. timestamp : Insights Time is epoc format ,  for ex ( "timestamp": "inSightsTime") 
9. uptool:   JsonArray maintaining parent relationship for ex (for JENKINS uptool can be GIT and is mentioned as uptool:["GIT"].
10. downtool: JsonArray maintaining child relationship for ex (for JENKINS downtool can be SONAR and RUNDECK and is mentioned as downtool:["SONAR","RUNDECK"].
11. inSightsTimeX: this is Insights Time.
12. author: auther name (Mandatory for the SCM category optional for other categories)

Summary Info Properties (Mandatory Property for summary information display )

1. message : array of message objects having 4 properties.
   1. Message : this is standard message shown on the screen , currently 3 standards messages are being supported.
      1. Commit Information - Commits performed over a period of {0} by {1} unique developer(s) (To be part of any SCM tool)
      2. Build Information - {0} Passed {1} Failed (To be part of any build tool)
      3. Deployment - {0} Successful Deployments {1} Failed Deployments (To be part of any deployment tool) 
   2. Operation : this is aggregation function name currently there are 2 operations supported .
      1. SUM : this operation is used to sum based on provided parameters.
      2. TIMEDIFF : this operation is used to calculate the diff in timestamp with provided input (To be part of SCM category)
   3. OperandName: this is the name of the property in datamodel on which the operation is performed for ex( if operation is TIMEDIFF and OperandName is timestamp then TIMEDIFF is calculated on timestamp )

   4. OperandValue: this is mandatory field for the SUM operation for ex ( Message Clause is : Deployment - {0} Successful Deployments {1} Failed Deployments and Operation is SUM and OperandName is Success then it is calculate the no of nodes having Success status and it value gets replaced in first place {0} and Total - Success nodes gets replaced in {1} 

UIFilter Properties (Mandatory Properties displayed in dropdown )

uifilter : Array of neo4j properties for ex (uifilter for the JENKINS could be "uifilter":["buildNumber","projectName"] meaning buildNumber and projectName is displayed on the UI dropdown

cardDisplayProps (Mandatory properties displayed on the card in traceability UI)

 a. it is json array mentioned in the traceability config holding list of properties (note that these properties name must match the traceability config properties)

excludeLabels : used to exclude unwanted property