comments are updating with wrong username in Azure Devops

[V V Satyanaraya]

Hello,

we have configured Azure DevOps integration with Agile Development using Microsoft Azure DevOps Integration for Agile Development plugin. We have successfully set up the connection between ADO and ServiceNow. Work items are passing and records are updating on both ends. 

If we are updating work notes at ServiceNow, it is updating comments with the name of the user who has created access token (PAT) in Azure DevOps. 

Is there any way to restrict this or is this supposed to be the expected behaviour ?

Thankyou!

[V V Satyanaray1]

it remains same, that is the behaviour of it comments which are passed from ServiceNow gets updated with the user name who has created PAT token. Better use unique service account only for this integration and create a PAT token from that account 

[test0413]

Hello,

we have also configured Azure DevOps integration with Agile Development using Microsoft Azure DevOps Integration for Agile Development plugin. Everything looks working fine except updating epic on user story is not updating in Servcienow when an Epic is linked to user story later after creating the story in Azure. Can you tell us how you acheived this?

Thanks!

[V V Satyanaray1]

both tables need to connected with ServiceNow and then the field mapping should be done properly.

[test0413]

Hello Satyanatay1,

both the tables are connected and mapping is done. Even thought field from Azure Epic is. not being puleld and updated in Servicenow. you ahve any idea why?

Epic has the field populated in Azure and teh same is empty in ServcieNow

Thanks in advance.

[V V Satyanaray1]

in the above scenario first a epic should be created in ADO and that will get synced to ServiceNow. similarly an incident should be created and this get synced to ServiceNow. Now if you are considering to tag incident under this synced epic you need to create a field in incident table and map this field with parent.system field w.r.t ADO once the mapping is done, in incident from if epic is selected as parent then in ADO this work item moves under the respective epic.

please mark this as helpful if solves your issue