Azure Devops bi-directional integration with Agile Development

Prabhh
Kilo Guru

‎05-20-2020 01:05 AM

Hello,

We have started configuring Azure Devops integration with Agile Development. We have successfully set up the connection between ADO and Servicenow. We have mapped ADO Epic to Project in Servicenow and upon creating an Epic in ADO, Project is successfully being created in Servicenow but when we create a Project in Servicenow, it is not creating any Epic in ADO.

It seems integration is updating records from ADO to Servicenow but not vice-versa. Can you please guide if any other configuration are required to export data from Servicenow to ADO?

- Prabhh

Labels:
0 Helpfuls
  • 2,123 Views
11 REPLIES 11

Sara3
Giga Guru

‎10-25-2024 12:29 PM - edited ‎10-25-2024 12:29 PM

We have finally gotten this integration working after MANY problems and not a lot of help from ServiceNow.  I will say that the documentation for this integration is terrible.  Also, they do not seem to be updating this integration, so please take that into consideration.  Hopefully this helps someone else as it took us tons of work to discover all of this information.   

Also, after all of this work, we recently found out that SAFe is being deprecated and we will need to move to Enterprise Agile Planning (EAP).  So, please take all of that into consideration when you are deciding whether to move forward with this integration.

The version of Azure DevOps that we were told to enter is very old, 4.1 - this is the indication that they aren't updating this integration.  This is even older than what is listed in their documentation.  However, it is what we received from their development team after opening a Support ticket when something wasn't working.

Sara3_12-1729884223132.png

 

 

__________________________________________________________________________________________________________

We are using the SAFe module and not the Agile Development module, so some of our configuration and mappings may differ if you are using Agile Development.

If you want to enable bi-directional integration, you need to have these enabled on your project record:

Sara3_0-1729882156474.png

 


Also, the mappings are very tricky.  We had the most problems with that.  I will add screen shots for your assistance.  

Sara3_4-1729883402610.png

Sara3_8-1729883775409.png

Sara3_9-1729883792374.png

Sara3_10-1729883810546.png

 

 

On fields with choices/states, you have to define the mapping for those as well. They will depend on how your company wants to map those.  Here is an example:

Sara3_11-1729883891188.png

 




Also, when testing, a helpful trick is to add the "external identifier" field to any list view table you are view records for (stories, epics, etc.).  It is a reference field that contains the information back to the imported record's information with links to the record in Azure DevOps.

Sara3_1-1729882659881.png

Sara3_2-1729882709906.png



We also found that we had to switch from using "description" to "HTML description"  field on several of the forms because the data coming from Azure DevOps was in html format and wouldn't show up in the description field until we switched to the HTML Description field.

Sara3_3-1729882863303.png

 

0 Helpfuls

Vishal36
Mega Guru

‎11-07-2024 04:06 AM - edited ‎11-07-2024 04:26 AM

Hi @Prabhh, 

Yes, it is possible to achieve this use case. Here is you can go about it: 

  • Enable Domain Separation: Firstly, you’ll need to turn on Domain Separation in the parent ServiceNow instance to manage data and permissions separately for each domain (like your child org). 
  • Check your contracts: Before diving in, double-check that your ServiceNow contracts allow for Domain Separation. Not all contracts are the same, so it’s a good idea to confirm this upfront. 
  • Merge both the instances for unified management: Use OpsHub Migration Manager (OMM) to merge the data: OMM (ServiceNow's Partner), is an enterprise - grade migration tool that supports robust data migration, allowing smooth transitions across instances with a focus on preserving historical data and configurations.   Note: The migration tool doesn’t handle domain-specific permissions. 
  • Set Up Permissions: After enabling Domain Separation in ServiceNow instance, set up separate roles and permissions for both domains.  

Potential Risks: 

  • Data Security: Improperly configured permissions can lead to unauthorized access to sensitive information.
  • Complexity in Management: Handling permissions and data flow between domains can become complex as your setup grows. 

If you want to learn more about OMM, feel free to contact us for an initial free consultation on migration planning with our solutions architects.

 

Thanks, 

OpsHub Team

0 Helpfuls