You should check the output files before you import them. Those files will show how you import into devops. You can check if the mapping was correct, and if that is so, check your devops settings and make sure it is OK. Also during import the warnings should be looked at. Or look at the output log for errors and warnings.

LikeLike

{
“source”: “Status”,
“target”: “State”,
“for”: “Bug”,
“mapping”: {
“values”: [
{
“source”: “OPEN”,
“target”: “New”
},
{
“source”: “IN PROGRESS”,
“target”: “Committed”
},
{
“source”: “CLOSED”,
“target”: “Done”
}
]
}
},

This is how i have mapped.
In jira the status is closed but in ADO it is showing as NEW or TO DO

LikeLike

When the export is done, carefully look at the files that have been created. You can examine those, and check whether the statuses and other attributes are what you expect them to be. You have to create the mapping for statuses that are not in the default settings.

LikeLike

LikeLike

LikeLike

I suggest you look at https://docs.microsoft.com/en-us/azure/devops/test/create-a-test-plan?view=azure-devops
I do not use test suites often so I don’t have any up-to-date knowledge of those suites.

LikeLike

LikeLike

Yes Peter! Thanks. Area path & Iteration path need to be configured at both project & team configuration. I was missing it from team configuration and so facing issue.

LikeLiked by 1 person

Hi Charu, If the items are imported, you should check Area Path(s) and Iteration Paths. There is a lot of documentation available, please look at: https://docs.microsoft.com/en-us/azure/devops/boards/backlogs/set-up-your-backlog?view=azure-devops.

Hope this helps!

LikeLike

LikeLike