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 08:32 AM
Plugin: Atlassian Jira Integration for Agile Development
Description:
When multiple Jira issue types are mapped to a single ServiceNow table, then Export and import of issues works based on the first created table and Field mappings records
Steps to Reproduce :
- Set up integration between Jira and ServiceNow
- navigate to table maps of any project
- Assume Story and Task (from Jira application) are mapped to the rm_story table in ServiceNow.
- 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 'Story' issue type in Jira Application.
- Reason: Story to rm_story mapping created first.
Expected Behaviour for Import
- Import of issue type 'Stroy' from Jira to ServiceNow (rm_story) works as expected.
- When a 'Task' issue is imported from Jira to ServiceNow, the field mappings of Task are neglected and Field mappings of 'Story' are considered and records are created based on 'Story' field mappings.
- Reason: Story to rm_story mapping created first.
Labels:
- 928 Views
Comments
Community Alums
Not applicable
- Mark as Read
- Mark as New
- Bookmark
- Permalink
- Report Inappropriate Content
09-27-2024
09:13 AM
We have same issue, when checked with ServiceNow they mentioned multiple issue type from Jira to ServiceNow is not compatible. We need to have separate tables for each issue types in Jira.
Have you found out an alternate solution for this?
