Skip to main content

When I import PBI from Azure Devops, the content of some of them is deleted. Only the PBI status remains displayed. ON ADO, I don't see any difference in the content of the PBIs, which are displayed correctly. 

 

 

Hi @Paul B 

The issue you're experiencing with importing PBIs (Product Backlog Items) from Azure DevOps into Lucidchart, where only the status is displayed and the content is missing, could be due to a few potential reasons. Here are some troubleshooting steps to resolve this:

1. Check Import Settings in Lucidchart

  • When you import PBIs into Lucidchart, make sure that all fields are selected for import, not just the status. There may be an option during the import process to choose which fields or details to include (e.g., title, description, status).
  • Ensure that fields like "Description" or "Details" are not excluded in the Lucidchart import settings.

2. Verify API Permissions

  • Check the permissions of the Azure DevOps API integration with Lucidchart. Sometimes, if the API access is restricted, it might not pull all data fields correctly. Make sure that the Lucidchart integration has permissions to read all necessary fields from the PBIs.

3. Update the Lucidchart and Azure DevOps Integration

  • Ensure that both Lucidchart and Azure DevOps are updated to their latest versions. Sometimes, compatibility issues can arise with older versions.
  • You might want to try reauthorizing the Azure DevOps integration with Lucidchart to refresh the connection.

4. Field Mapping Issues

  • It's possible that there is a mismatch in how the fields are mapped between Azure DevOps and Lucidchart. Check if Lucidchart allows you to configure or customize field mappings during the import process.

5. Check for Custom Fields in ADO

  • If your Azure DevOps setup includes custom fields, there might be an issue with how these fields are being interpreted by Lucidchart. Even if the PBIs appear identical in ADO, differences in how custom fields are used or structured could cause inconsistencies during the import.

6. Contact Lucid Support

  • If the issue persists, it might be a bug or limitation with the integration. Reach out to Lucidchart support for more specific guidance and to see if there’s a known issue or patch available for this behavior.

I hope this helps.

Regards, 

Ria


Hi,
I've applied your advice, but it doesn't work. On the other hand, I can see that the problem comes from older PBIs.  When I make a copy, it's displayed correctly. When I edit the details of the card, I notice that the organisation of the fields is not the same.
 

 


Hi @Paul B, thank you for posting in the community! Just to confirm, is this happening in boards with existing ADO cards that were imported in the past? It sounds like the existing cards are no longer displaying the details - is this correct? 

If you haven’t already, could you please try importing ADO cards in a new blank Lucidspark board and let me know if the issue persists there.

This information will help us better understand the issue and narrow down any potential causes. 

Thanks in advance for your help and please let us know if you have any questions! 


Hi Leianne.

In the first few seconds of integrating these problematic PBIs, the details of the card are well displayed with the new version. But after synchronisation, the title disappears and the details show the old version.
1- I'm almost certain that these are PBIs that have already been imported with the old version.
2- However, I also duplicate my boards, and this may also be the reason for the malfunction.   In fact, when I create a blank board and import an old PBI, the display is correct, even after synchronisation.


Hi @Paul B, thank you for sharing that additional information. I’m glad to hear the issue doesn’t happen in a new blank board. It looks like this may be related to the imported cards from new and old ADO applications.

I am investigating this internally and will update this thread as soon as I have more details. Please let us know if you have any questions in the meantime. Thanks! 


Hi @Paul B, thank you for sharing that additional information. I’m glad to hear the issue doesn’t happen in a new blank board. It looks like this may be related to the imported cards from new and old ADO applications.

I am investigating this internally and will update this thread as soon as I have more details. Please let us know if you have any questions in the meantime. Thanks! 

Any updates? I see the same problem in LucidSpark.


Interesting, because I can copy and paste the card here and it displays: 0_0?a=58570&x=-37921&y=-10304&w=270&h=137&store=1&accept=image%2F*&auth=LCA%206fe876b0c6f6238a460ee979a88a7c04cef184c3cd4bc7e54f98efef2e6958c4-ts%3D1732740717

 

But what I see in Lucid is this:

It seems to just be a rendering or display issue and not an integration issue.


In case this helps in trouble shooting and recommending a fix for me...

 

Screenshot immediately after I imported 181cards 

 

 

Screenshot of cards after less than 1 minute

None of the ones that are still displaying correctly had been imported previously using the old integration. All of the ones that do not display correctly had been previously imported using the old integration.  

I also noticed that if I tried removing the card imported with the old integration and then imported  the same card with the new integration, it did not help. The card info disappeared after about 30 seconds.


Hi @Paul B 

The issue you're experiencing with importing PBIs (Product Backlog Items) from Azure DevOps into Lucidchart, where only the status is displayed and the content is missing, could be due to a few potential reasons. Here are some troubleshooting steps to resolve this:

1. Check Import Settings in Lucidchart

  • When you import PBIs into Lucidchart, make sure that all fields are selected for import, not just the status. There may be an option during the import process to choose which fields or details to include (e.g., title, description, status).
  • Ensure that fields like "Description" or "Details" are not excluded in the Lucidchart import settings.

2. Verify API Permissions

  • Check the permissions of the Azure DevOps API integration with Lucidchart. Sometimes, if the API access is restricted, it might not pull all data fields correctly. Make sure that the Lucidchart integration has permissions to read all necessary fields from the PBIs.

3. Update the Lucidchart and Azure DevOps Integration

  • Ensure that both Lucidchart and Azure DevOps are updated to their latest versions. Sometimes, compatibility issues can arise with older versions.
  • You might want to try reauthorizing the Azure DevOps integration with Lucidchart to refresh the connection.

4. Field Mapping Issues

  • It's possible that there is a mismatch in how the fields are mapped between Azure DevOps and Lucidchart. Check if Lucidchart allows you to configure or customize field mappings during the import process.

5. Check for Custom Fields in ADO

  • If your Azure DevOps setup includes custom fields, there might be an issue with how these fields are being interpreted by Lucidchart. Even if the PBIs appear identical in ADO, differences in how custom fields are used or structured could cause inconsistencies during the import.

6. Contact Lucid Support

  • If the issue persists, it might be a bug or limitation with the integration. Reach out to Lucidchart support for more specific guidance and to see if there’s a known issue or patch available for this behavior.

I hope this helps.

Regards, 

Ria

This response is exactly what Chat GPT told me and is quite useless. Not only that, you mention Lucid Chart, and not Lucid Spark. Is there an integration with DevOps and Lucid Chart?


Hi ​@sproffit, thanks for posting in the Lucid Community! Since this seems specific to your document or account, I have converted your post to a private ticket so our support team can help you further and take a closer look at the issue. 

The team works through tickets in the order they are received, and you can expect a response to your email associated with your Lucid account. Please refer to that email for further correspondence.


Reply