Sembra che la pagina che stai cercando non sia tradotta, abbiamo però altri contenuti in italiano e offriamo assistenza.
Naviga nel portale di assistenza in italianoInvia una richiesta
Come possiamo aiutarti?
Learn. Share. Discuss.
Enable additional creation parameters on the inbound Azure DevOps sync so Epics, Features, Bugs, etc. are the same item type in Wrike. Out of the box, regardless of what work item type you import, it gets created as a Task in Wrike. 
Folllowing List for Post: Azure DevOps Sync Fix
[this list is visible for admins and agents only]
Hi Laura Lysaght, thank you for sharing your feedback! I'll send it to the Integrations team 👍 Let me know if you need help with anything else 🙂
Lisa Community Team at Wrike Wrike Product Manager Become a Wrike expert with Wrike Discover
Lisa Wrike Team member Become a Wrike expert with Wrike Discover
Thanks Lisa! If anyone in the integrations team would be willing to demo an existing ADO integration, I'd love to learn from their experience.
Laura, you can create custom Item types and then update them to work like ADO. But I'm trying to find other users like me who are trying to set this up.
Thanks for the feedback! I'll give it a try. I don't have a solution yet. My current constraint is that each ADO sync is limited to one location. So 1 ADO project to my whole Wrike Space "Project" Folder is a no-go because I have multiple ADO projects 🤷♀️
What do you mean that each ADO sync is limited to one location. Our project entails many teams. so In ADO I have one main project but each team has their own board. Then in Wrike I broke down the teams into separate Epics - using the Custom Item Type.
Hey Sunnie Lewis you've probably already have something figured out, but I found it best to set up a sync manually for each Wrike Project to a unique AzDO Area Path. Technically that's not how AzDO uses Area Paths, but it works best for me.
No we did not figure this out. We determined that this wouldn't work for us properly and have gone in a different direction entirely.
Basudha Sakshyarika Community Team at Wrike Wrike Product Manager Conosci le straordinarie funzionalità di Wrike e le best practices
Basudha Sakshyarika Wrike Team member Conosci le straordinarie funzionalità di Wrike e le best practices
At this time, we no longer have the time to spend working on that solution. As I stated before we're heading in a new direction due to internal time constraints.
Sunnie Lewis, thank you for keeping us informed. Please feel free to let us know if there's anything else we can assist you with.
Rohan V Community Team at Wrike Wrike Product Manager Conosci le straordinarie funzionalità di Wrike e le best practices
Rohan V Wrike Team member Conosci le straordinarie funzionalità di Wrike e le best practices