Overview
Please follow the instructions in the main Azure DevOps integration guide for setting up the overall integration:
https://spiradoc.inflectra.com/External-Bug-Tracking-Integration/Using-SpiraTest-with-MS-TFS/#configuring-the-plug-in
ADO Standard Fields
When you need to map a custom property in Spira to a standard field in Azure DevOps, please use the list of fields here:
https://spiradoc.inflectra.com/External-Bug-Tracking-Integration/Using-SpiraTest-with-MS-TFS/#tfs-field-reference
For example, you can map:
Spira Custom Property | Azure DevOps 'External Key' |
---|
Application Type | Microsoft.VSTS.Feedback.ApplicationType |
ADO Custom Fields
When you need to map a custom property in Spira to a user defined field in Azure DevOps, the process is the same overall, but getting the "system name" for the field is different, because Azure DevOps does not always show the system names directly.
https://docs.microsoft.com/en-us/azure/devops/boards/work-items/work-item-fields?view=azure-devops
When you add a custom field to an inherited process, Azure DevOps assigns a reference name based on the process name and the name of the field. For example, you add a field named Triage to the My Agile process, the reference name is MyAgile.Triage. No spaces are allowed within the reference name.
So in Spira you might map:
Spira Custom Property | Azure DevOps 'External Key' |
---|
My Field | MyProcess.MyField |
You cannot simply use the display name:
Spira Custom Property | Azure DevOps 'External Key' |
---|
My Field | My Field |
(this is incorrect and will give errors)