Rishi1
ServiceNow Employee
Options
- Post History
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
on 06-13-2021 09:22 AM
Plugin: Microsoft Azure DevOps Integration for Agile Development
Description:
When multiple Azure DevOps work item types are mapped to a single ServiceNow table, then Export and import of work items works based on the first created table and Field mappings records
Steps to Reproduce :
- Set up integration between Azure DevOps and ServiceNow
- navigate to table maps of any process type
- Assume 'User Story' and 'Task' (from Azure DevOps application) are mapped to the rm_story table in ServiceNow.
- User Story mapped to rm_story (table and field mappings created first)
- Task mapped to rm_story
Expected Behaviour for Export
- When a new story is created in ServiceNow, it is exported as a 'User Story' work item type to Azure DevOps Application.
- Reason: User Story to rm_story table mappings created first.
Expected Behaviour for Import
- Import of work item type 'User Stroy' from Azure DevOps to ServiceNow (rm_story) works as expected.
- When a 'Task' work item is imported fromAzure DevOps to ServiceNow, the field mappings of Task are neglected, and Field mappings of 'User Story' are considered and records are created based on User story field mappings.
- Reason: User Story to rm_story table mappings created first.
Labels:
Comments
RiteshSwarnakar
Giga Guru
- Mark as Read
- Mark as New
- Bookmark
- Permalink
- Report Inappropriate Content
08-05-2023
04:49 AM
The above mentioned issue can be fixed.
Please refer Issue 5 in the below article:
Map all the fields from both external tables in both the field mapping for each table.
The fields which are not present in other work item will get ignored.