Skip to main content
Solved

ADO cards not resolving area path

  • April 14, 2026
  • 3 replies
  • 24 views

Forum|alt.badge.img+1

This seems very similar to this post, but that did not seem to get to a resolution, so I’m opening another for my scenario:

We are using the Azure DevOps Cards extensively and we have started seeing issues with Area Paths showing up as numbers rather than the Display Name.

For example, this area path should be showing “Redwood”
 

 

We have tried the following, but none of these have changed the behavior we are seeing:

  • Unlink/relink to ADO
  • Create a new fresh Lucid Spark board from scratch
  • Try in multiple different browsers (Chrome, Edge, Firefox)

We are getting the same “number” in all cases.  The part that is confusing is that some area paths DO work and show the display name correctly.  But most of them in our system are showing only as numbers.

 

As further background,  I can see the area paths in the import screen by display name.  For example:
 

I can also inspect with F12 web browser console and see the actual area paths coming back in the payloads from ADO.

Best answer by Leianne C

Hi, ​@tim.mcdougall, thanks for getting back to me with that additional information. I believe you have identified a bug, and I have reported this to our development team. I apologize for any disruption this may cause, and I will update this thread with any new information about a fix. Please follow along on this thread for updates, and post any additional questions or concerns below.

Comments

Leianne C
Forum|alt.badge.img+15
  • Lucid support team
  • April 27, 2026

Hi ​@tim.mcdougall, thank you for posting in the community and sorry for the delayed response. I’m checking this behaviour internally and will share more information here as soon as possible. 

Please feel free to let me know if you have any additional questions in the meantime. 


Forum|alt.badge.img+1

Hi ​@tim.mcdougall, thank you for posting in the community and sorry for the delayed response. I’m checking this behaviour internally and will share more information here as soon as possible. 

Please feel free to let me know if you have any additional questions in the meantime. 

Thanks for the update.  I just double-checked our system to confirm we are still seeing the same behavior.  Let me know if there is any info you need to help with the investigation.


Leianne C
Forum|alt.badge.img+15
  • Lucid support team
  • Answer
  • May 1, 2026

Hi, ​@tim.mcdougall, thanks for getting back to me with that additional information. I believe you have identified a bug, and I have reported this to our development team. I apologize for any disruption this may cause, and I will update this thread with any new information about a fix. Please follow along on this thread for updates, and post any additional questions or concerns below.