You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
When working on a diagram there are often many small changes that are made. It's challenging to separate large milestone source revisions that should be used for various releases when there is no way to name a revision.
Describe the solution you'd like
Being able to name/rename revisions directly in draw.io or through the "Manage Versions" window in Google Drive would both be helpful.
Describe alternatives you've considered
This is similar to source tags vs. binary releases - the binary releases (exported images/PDFs) are helpful for end users to consume, while the source tags in the actual diagram revision history is useful for people working on the diagram to see history and understand what changed/when, maybe even compare/restore large chunks from old milestones.
Additional context
N/A
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. See the FAQ for more information.
Thanks for the suggestion. Unfortunately, the request didn't gain enough interest over the open it was open to justify the effort of implementation and maintenance.
Is your feature request related to a problem? Please describe.
When working on a diagram there are often many small changes that are made. It's challenging to separate large milestone source revisions that should be used for various releases when there is no way to name a revision.
Describe the solution you'd like
Being able to name/rename revisions directly in draw.io or through the "Manage Versions" window in Google Drive would both be helpful.
Describe alternatives you've considered
This is similar to source tags vs. binary releases - the binary releases (exported images/PDFs) are helpful for end users to consume, while the source tags in the actual diagram revision history is useful for people working on the diagram to see history and understand what changed/when, maybe even compare/restore large chunks from old milestones.
Additional context
N/A
The text was updated successfully, but these errors were encountered: