+1

We are piloting a wiki-based approach to documentation.  The wiki uses Markdown and lives in a Git repository so we can have a "published" version and we can have one or more working versions.  The problem comes with the "live" published images from Lucidchart.  In order to keep the versions of the wiki in sync with their appropriate versions of the diagrams we have to export the images out of Lucid and into the wiki images folder.  Who needs that noise? 

As Jonas suggested above if you let us publish specific snapshots of diagrams as an image instead of just a "live" image we could still use only URLs for images in the wiki but we could use version-specific URLs.  (And you know avoid that whole export/import image thing.)

Respectfully

Charles S.

Same need on our side I'd like to be able to keep the documents in LucidChart and avoid exporting a specific version to ensure there is only one place to update.
A simple linking capability to a named version would address our need.

Actually even being able to specify the sheet to open would be amazing.

We need this as well.  The ability to link to a static version that represents the current state of the code at that point in time is hugely valuable.  Used in conjunction with the Lucid 'diff' tool it provides us with a VERY powerful way to track changes.  If there is no way to track the version of the code then the git 'integration' is not of much use at all.

+1

Echoing my desire for this feature.

It would be amazing to be able to have the Confluence plugin display a diagram at a specific: version page position/zoom. Failing that at least the ability to copy a URL to a specific version of a diagram.

Hey there thank you for posting in the Lucid community! Our sincere apologies for the delayed response on this thread - I wanted to follow up in case this answer may still be useful to you and to provide a solution for other users who see this thread in the future.

Thank you for your request for sharing or publishing to a specific document version! We're always looking for ways to improve Lucidchart and your feedback is the best way for us to keep developing a useful and effective product. I've gone ahead and submitted your idea to our product team on your behalf and it will be taken into consideration when prioritizing improvements. 

We would also love to hear additional detail about your use case or see an example of what you're hoping to achieve in the thread below. Additionally if you've discovered a workaround to achieve something similar in the meantime we'd love to hear about it! Thanks for your request!

RE: https://lucidchart.zendesk.com/hc/en-us/community/posts/360077380752/comments/4464249875860

Use case: This feature would allow us to tie versions of a lucid design into specific versions in a versioning repository.  As the design matures it can be tied to other versioned artifacts and older versions of the design will remain tied to older implentation artifacts.

@mike h102 Thanks so much for sharing additional detail - we'll ensure this is available to the development team as they consider improvements to the product!

Referencing named versions externally (via url for example) would really be an amazing feature for documenting evolution of diagrams and allow a good connection to other systems.

Hi Martin 

Thanks for the additional context! I'll make sure to add those details to this feature request!

Yes this would be an amazing feature. Would likely necessitate the ability to add the version number to a diagram via Formula.

Any update on this feature request? This would be a super valuable feature

Hi Nick

Thanks for adding your support for this feature. There are currently no updates but we have added your feedback for review by our development team. 

Hello all 

+1

This will be super usefull for our team. 

Hi Mateusz

Thanks for chiming in! The best way to send feedback to our Product Development Team is to upvote! The more requests they receive for the same feature the more likely it is that it gets prioritized.

@Coumba.

Thank you.

@Coumba D : Instead of creating duplicate ideas, I think it’s good if users “chiming in with +1” are encouraged to upvote. I.e.: “Make sure to show your support for great ideas by upvoting them.”.

@Jonas L Thanks for your comment! Fortunately in our new community platform we launched a few weeks ago, we now have upvoting functionality that can capture these “+1” comments and are no longer collecting requests externally. I’ve updated the comments in this thread to reflect that. I appreciate you weighing in on this process and hope you find that this makes it easier to capture ideas from all users. 

This feature will be definitely useful for versioning the documents 

Hhi ​@Velmurugan M, thank you for adding your feedback to this thread! This is incredibly helpful to our product development teams as they gauge interest for features and continue to research product enhancements. 

The lack of this capability is limiting our use/adoption of lucid. Having the version history and ability name versions is great - but without being able to deep-link to them from external documents it removes the value.

Even adding the ability to add an action that takes a person straight to a previous version would be an improvement.

Hi ​@johncat, thank you for showing your support for this request by upvoting this post and adding to this thread. I can certainly understand why this is important. 

We encourage anyone else who’s interested in this to upvote this post and share any additional details about your use case or what you’d like to see in this experience. For more information about how we manage feedback in this community, please take a look at this post: