Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TF201077: The work item type Product Backlog Item cannot be found. #37

Closed
eeerrrwwwuuu opened this issue Mar 19, 2019 · 2 comments
Closed

Comments

@eeerrrwwwuuu
Copy link

I'm having some problem with Importing tickets from JIRA due to problem with mapping types.

  "type-map":{
    "type": [
      {
        "source": "Feature",
        "target": "Feature"
      },
 .....
      {
        "source": "Story",
        "target": "Product Backlog Item"
.....
      {
        "source": "Task",
        "target": "Product Backlog Item"
      }

ech of tickets stored in Json starts with :

{"Type":"Product Backlog Item", "OriginId":"ITSWBIOE-721","WiId":-1, 

what leads to an error

[Microsoft.TeamFoundation.WorkItemTracking.Client.WorkItemTypeDeniedOrNotExistException] TF201077: The work item type Product Backlog Item cannot be found. It may have been renamed or destroyed.:
   w Microsoft.TeamFoundation.WorkItemTracking.Client.WorkItemTypeCollection.get_Item(String typeName)
   w WorkItemImport.Agent.CreateWI(String type)
   w WorkItemImport.ImportCommandLine.ExecuteMigration(CommandOption token, CommandOption url, CommandOption configFile, Boolean forceFresh)

If I understand it correctly, there's no match in target schema for this type, I believe I should remap it somehow ? I was thinking about :

     {
        "source": "Story",
        "target": "User Story"
      },

and

      {
        "source": "Task",
        "target": "Task"
      },
@MOlausson
Copy link
Member

Hi @eeerrrwwwuuu, you are right that if the work item types don't exist in your target azure devops project (like Product Backlog Item in your case) it will err out and agree that the error could be better. I'll see if we can improve that.

But the solution is as you describe to map to the correct types (User Story in your case).

@MOlausson
Copy link
Member

Fixed in release 2.2.x

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants