Hi,
I noticed that in Lucid Card (created via Jira import), after a project change in Jira that changes the ID of the issue, Card in Lucid is broken and only shows warning sign with no means to update it. Jira itself redirects to the issue in the other project.
If there was a Jira’s issue id field exposed in UI, we could just update it. Now we need to locate those manually and reimport them.
Hi
Finally, for more information on how Lucid manages feedback via this community, take a look at this post:
Thank you for sharing your feedback and ideas in the community. Please let us know if you have any questions.
+24Hi
This issue occurs because LucidSpark/Lucidchart stores Jira references from the original instance, so moving to a new Atlassian instance or changing project IDs breaks those links and prevents updating them in the UI. At this time, to mitigate this try to manually reconnect or re-import the Jira cards using the new instance or updated issue keys.
To learn more - LucidSpark Jira Cards not letting me switch to a different Atlassian Instance | Community
Hope this helps - Happy to help further!!
Thank you very much and have a great one!
Warm regards
+15Hi
Finally, for more information on how Lucid manages feedback via this community, take a look at this post:
Thank you for sharing your feedback and ideas in the community. Please let us know if you have any questions.
A Lucid or airfocus account is required to interact with the Community, and your participation is subject to the Supplemental Lucid Community Terms. You may not participate in the Community if you are under 18. You will be redirected to the Lucid or airfocus app to log in.
A Lucid or airfocus account is required to interact with the Community, and your participation is subject to the Supplemental Lucid Community Terms. You may not participate in the Community if you are under 18. You will be redirected to the Lucid or airfocus app to log in.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
