Versions Compared

Version Old Version 14 New Version 15
Changes made by

Jeyanthi (Unlicensed)

Gaurav (Unlicensed)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Anchor
top1
top1


Tip

The Traceability Dashboard gives detail information of entire DevOps journey in pipeline view

Navigation : Dashboard Groups → Traceability Dashboard 


Introduction :

Traceability is the ability to relate and document all activities of application delivery, which can then be traced both forward or backward from its origin. Requirements traceability help teams to get insights into indicators such as quality of requirements or readiness to ship the requirement.
Traceability report from top level work item to the granular level item along with any artifacts i.e. change requests, user stories, code commits, quality check, deployment etc.
Traceability highly beneficial for tracing end-to-end pipeline and help us to improve our system.


       datamodel
Panel

Configuration : 

Below are the pre-requisites to be setup in order to view Traceability dashboard .

          datamodel
  •  
  • Change property as per client pipeline. 
  • Once It configured, upload it in Insights application using Configuration File Management menu, for more detail read Configuration File Management
  • Traceability.json file has structured format and having collection of JsonObject as below.(Sample Ref)
  •    
      {
         
Expand
titleSample Traceability.Json

{
"JIRA":{

         

"uuid":"uuid",

         

"order

" :1,
         

":2,
"displayText":"Issues",
"category":"ALM",
"issueKey":"key",
"property":"categoryName",
"epicKey":"epicKey",
"issueType":"issueType",
"toolName":"toolName

",
          "toolstatus": "jiraStatus",
         

",
"creationDate":"creationDate",
"resolutionsdate":"resolutionsdate",
"issueStatus":"status",
"author":"reporter",
"projectName":"projectName",
"timestamp":"inSightsTime",

         

"priority":"priority",
"inSightsTimeX":"inSightsTimeX",

         

"eventKey":"eventKey",
"uptool":[
"

null

EPIC"
],

         

"downtool":[
"GIT"
],

          "uifilter":["jiraKey","projectName"],
           },
         

"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":

2

3,
"displayText":"Commits",

         

"inSightsTimeX":"inSightsTimeX",
"commitId":"commitId",

         

"property":"categoryName",
"toolName":"toolName",

         

"

toolstatus

commitStatus":"

Committed

status",

         

"author":"

gitAuthorName

authorName",
"repositoryName":"repoName",

         

"timestamp":"inSightsTime",

          "uptool":["JIRA"],
          "downtool":["JENKINS"],
          "gitCommiTime":"gitCommiTime",
         

"jiraKey":"jiraKey",
"gitCommiTime":"gitCommitTime",
"uptool":[
"JIRA"
],
"downtool":[
"JENKINS"
] ,
"messages":[

           

{
"Message":"

Commit Information - Commits performed over a period of

Total {0}

by {1} unique developer(s)

Developers ",
"Operation":"

TIMEDIFF

DISTINCT_COUNT",
"OperandName":"

timestamp

author",
"OperandValue":

"

[
]
}

           

],

         

"uifilter":[
"commitId"
]


         }

         

Info
titleKeys in datamodel.json is sent to UI and values are the keys of neo4j nodes which is turn replaced by values of neo4j node

,
"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

Note
titleApart from the above mandatory properties other extra properties also can be mentioned in the datamodel as key can any string and value is the neo4j property
Steps to follow on UI
  •  

    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 

        

    UI Dashboard

    1. From the first dropdown select the tool name .(Jira as selected below)
    2. From the second drop down select the property for the tool name (this dropdown is loaded from the datamodel Traceability.json uifilter property)(jiraKey as selected below)

    3. paste the value of the selected property (

      LS-9974351736

      PS

      as pasted below)

    4. click on the submit button to get the pipeline view
Image Removed
    1. Summary viewImage Added
    2. Select Another Tab for pipeline view
    3.   Image Added
    4. Click on each tool name to get more detail for that property, User also can search record if needed Image Added
    5. Click on any card to d Image Added
    6. Click on more info of each tab to show more property Image Added


     

     

Back to Top