Lucid Cards imported from Azure Devops haven't story points and tags

Hi @Dawid, thank you for posting in the community! As it currently stands, no matter what you have in ADO, we will always map "Effort" fields to "Story Points". If "Effort" is missing then nothing will display within Lucidspark (even if points are not missing), which I suspect is what is occurring here. So, currently only Effort (from ADO) will show up in Lucid for a feature card.   

For ‘set Row’ as tags, would you mind sharing a screenshot of the issue so that I can take a closer look? 

Thanks in advance for your help. Please feel free to let me know if you have any questions! 

@Leianne C 

I can’t show all my tasks but let’s say I have two tasks with Tags `Tech Debt

` and `Must have` 

I import it as Dynamic Table and set Row to `Tags` and instead has there two rows `Tech Debt` and `Must have` I have one `Not Set`

@Leianne C 

But why you map "Effort" fields to "Story Points" instead just use `Story Points`? I think it’s more logic to use field `Story Points` as `Story Points` not `Effort`

@Leianne C Any update?

Hi @Dawid, apologies for the delay as I clarified this with our development team.

I have heard back from the team and they confirmed that it is currently expected for “Effort” to be mapped to “Story Points” - unfortunately I’m not able to share any additional information about this. 

Regarding the issue you raised with tags, the behaviour you are experiencing is expected as Tags from ADO are not currently supported in Lucid. The ‘Tags’ option shown in the Dynamic Table refers to the Tags feature in Lucidspark. I’ve added an example screenshot demonstrating this:

Thank you for your patience and please let us know if you have any additional questions! 

Hi @Dawid, I just received an update from our development and wanted to confirm that our team is actively working on the Azure DevOps integration.

We’re very interested in your feedback and committed to continually improving our products. If you’re willing to share, we’d love to hear more details about your use case or what you’d like to see in this experience within this thread. I’ve also converted this post to an idea so that it’s visible to others within the Product Feedback section of the community - from here, they can upvote it and add details of their own.

Finally, for more information on how Lucid manages feedback via this community, take a look at this post:

We appreciate your willingness to provide your requests and feedback in the Lucid Community!

Firstly, the Lucid Card dynamic table does not show history points, only priorities are visible. Secondly, when I try to set strings as tags, all tasks are shown as the "Not Set" group, even though they are assigned tags in ADO. This is likely due to incompatibility of data formats or settings between Lucidspark and ADO.

Hi @Dawid and @AlannaSantiago! Abby here from Lucid. Thank you for sharing your feedback. I thought the two of you, and others who might come across this topic in the future, might be interested in Lucid’s Agile Trusted User Group. This group is made up of passionate, experienced users who regularly use agile methodologies in their work. As part of this group, you’ll have the opportunity to connect directly with Lucid’s product team and share insights about your workflows, pain points, and needs, shaping the future of Lucid’s agile tools. 🎉 You can learn more and apply here. Thanks!