Skip to main content

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 ​@Lukasz 

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


Hi ​@Lukasz, thanks for your post! This is currently expected behaviour when changing projects in Jira. However, 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:

Thank you for sharing your feedback and ideas in the community. Please let us know if you have any questions.