I have an integration between ADO and Lucid that is great. Names, dates, and status are all updated on the card. Your ability to show a long-term view is so much better than anything in ADO. Love it. What doesn’t update is the Iteration or Sprint.

I can understand that the sprint/iteration is different from the date range, and that the date range makes more sense for the Timeline chart. However, my team does not work with date ranges but rather which sprint it falls into. A Task is meant to fall into a sprint, and normally a Product Backlog Item (PBI) is too, whereas Features are typically multi-sprint.

Perhaps what I’m looking for doesn’t integrate so well. I want the starting date for a work item to be based on the sprint start date (and therefore align with the Iteration Path), and the ending date to be based on Target Date. In ADO, there is no correlation defined between work item start date and Sprint Start Date and maybe that is the root of it.

It would be amazing that as Features and PBIs have their sprints updated during sprint planning that they also get updated in the Timeline chart in LucidSpark. That is the end goal.