Failed to Create ADO Work Items from Cards

Hi ​@Astrid_G, thank you for posting in the community. As a first step, would you mind sharing the following information to help us better understand the issue you’re experiencing? 

• Could you confirm if the affected item types are custom item types?
• Could you confirm if your mandatory fields are custom fields?
• A screenshot of the associated Javascript Console output after reproducing the issue. You can open your Javascript Console by pressing Ctrl+Shift+J (if your computer is a Windows/Linux) OR Cmd+Opt+J (if your computer is a Mac).
• Could you also try this in a new blank board to see if the issue persists there? 

Thank you in advance for your help and patience. Please let me know if you have any questions in the meantime!  

Hi ​@Leianne C 

1. Its a standard WIT - User Story
2. Two of the mandatory fields are custom, one is freeform text, one is a choice field.
3. Here’s the java screenshot

4. Same problem persists in a new blank board.

Hi ​@Astrid_G, thank you for sharing the additional information. I am looking into this on my end and will share an update here as soon as I have more details.

Please let me know if you have any questions or concerns in the meantime! 

Hello ​@Leianne C 

I wouldnt expect to have to specify the state for an item being created, as ADO always defaults that to New.
All of the mandatory fields (2 custom and 1 standard - target date) are being pulled in to the card for populating, for a User Story.

I have been able to create a Feature (which has no mandatory fields), so the integration is working at the basic level.

When I made the Target Date mandatory for the feature, and tried to create another one from ADO it failed the same as the User Story.

I made the Target Date optional again for the feature, and made the custom field (choice list) mandatory instead.  that field was pulled into ADO and with the choice made a new card could be created.
 

So the problem seems to be standard date fields that are mandatory.  I tried with both the default 00:00 timestamp and a specified time, as well has having the date set and neither worked.