Share via

Issue with Importing New Test Cases into Azure DevOps: "Invalid Workitem Field Values Found" Error

Potashnik, Irena 30 Reputation points
2024-05-28T19:44:04.2666667+00:00

I am facing some challenges importing test cases into ADO using CSV or XLSX files. It worked before, but now it has stopped working. The only way it works now is when I manually create empty test cases and put the IDs in the imported file. In this case, ADO updates the existing test cases with all the fields from the file. For some reason, ADO has an issue creating new test cases.

I tried exporting test cases to a file, removing all IDs, and then importing the same file into a new test suite. However, I get the following error when importing the file: "Error occurred while importing one or more test cases: Invalid workitem field values found."

How can I resolve this issue and successfully import new test cases into ADO without manually creating them first?

Community Center | Not monitored

4 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Sean deGroote 35 Reputation points
    2024-10-24T16:14:12.4133333+00:00

    I had this same issue today. Turns out that someone had added "Ready" as the status in the CSV. Changing this to "Design" worked. Has nothing to do with the Work Item Type column - silly Azure DevOps!

    User's image

    6 people found this answer helpful.
  2. Louay Al-Jondi 25 Reputation points Microsoft Employee
    2024-10-17T12:18:20.71+00:00

    I managed to export test suites from Nuance ADO and import them to Microsoft ADO with no errors, for successful import, you need to follow these steps. (This can apply to any TM tool qtest, silk central...etc)

    1. The csv file can have only these fields: ID, Work Item Type, Title, Test Step, Step Action, Step Expected, Priority.
    2. The ID field must have NO values, because ADO assigns new ID to every imported test case, since it’s new to the test suite
    3. For test cases that have Shared Steps as Work Item Type: Shared steps name need to be removed, or the import will fail. The error I found that Shared step is not a valid value to Work Item Type. The Test Case name is the only value supported in Work Item Type
    4. If you need Shared Steps, it’s better and easier to create them later after the import
    5. Solution: We need to modify each CSV to make it ready to be imported, by satisfying the conditions mentioned above
    6. I wrote a C# script to modify the CSV files to make ready for the import. If people interested, I could demo it

    3 people found this answer helpful.
  3. Christoph 5 Reputation points
    2024-10-22T14:42:38.19+00:00

    Is there any solution regarding this problem? I am still facing this issue in Azure DevOps. When I try to import new test cases there always comes an error showing: "Error occurred while importing one or more test cases: [object Object]" Do you have any hints?

    1 person found this answer helpful.
  4. Reimon Gonçalves 0 Reputation points Microsoft Employee
    2024-05-28T19:59:49.0733333+00:00

    The issue you're encountering when importing test cases into Azure DevOps (ADO) might be related to various factors, such as incorrect field values, mandatory fields not being filled, or field constraints.

    Check logs and error messages: Note the detailed error messages provided by ADO during the import process. They often provide specific information about which field or value is causing the problem, and post here.

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.