Tag note to a version

On our radar

It would be really useful to be able to tag a particular version with a note so that "working" copies can be identified for later reference when comparing with or restoring to an earlier version.

It would also be useful to be able to delete (or at least hide) intermediate versions that just add to the clutter when looking for a previous revision.

Created on 5 May 2018
Comments (5)

Changed the category to Lifetime

Hi Lester, 

Thank you for submitting your idea!

Currently, in LifeTime, you have the capability to add a description on tags. Let me know if you feel that is something missing. 

Thank you,

Joao Bento

Thanks, Joao for your pointer to the Lifetime support for tags but this does not appear to be what I was contemplating.

From Service Studio, if I click on "Open other version...", I get a list of every 1-click publish I have performed with just a version id, a timestamp and a user name (and a Yes indicator invariably on the top one coz it was published)

What I am suggesting is a way of adding a simple brief note to any of these entries (after publish) so that I know which ones I can trust if I have to revert back to one or refer to some change I did earlier.  It is not a matter of naming a specific working version when I release to production or anything that complicated.  Just a simple way of marking a version I consider useful to refer back to later whether it is a production ready version or not.

Particularly when I am about to embark on a particularly code-breaking change during development, I may want to return to a previous incarnation to cancel what I have now broken or simply for reference as to how it was done previously.  I tend to scribble down the ref id or time or try to remember date/time of a previously "acceptable" version for this purpose.  It would be great to simply tag a brief note to any version for easy visibility of change history by going to "Open other version" rather than needing to go through all the hoops of Lifetime.  I don't consider that an easy way to maintain or view change history.  It may be ok for final release versions but not for the many iterations made during development where tens or even hundreds of releases can be published in a few days.

This all came about recently as I essentially tried to create a new BRANCH to my development.  After a couple of days of breaking changes, crisis demanded I return to the previous version and just implement a few of the new changes.  Luckily it was easy to return to the known date of first change and the "Compare to other version" was great in allowing some of the new changes to be retro-fitted.

Now after a few more versions testing and fixing I have "lost" the point at which I reverted (ie the top of my broken branch) making it awkward to find it again.  A simple note would have made it obvious.

I suppose what I'd really like to see in the source control is a way of handling branches properly but a simple text note would be an easy alternative.

I hope I have explained myself a little better.

Changed the status to
On our radar

Hi Lester,

Sorry I realized that I've not updated this thread at that time. 

Thank you for your response, it was very clear and useful. 

Just to let you know that we have discussed this topic during this time and I'm quite confident that we will address your need.

We'll keep you posted as soon as we have more info. 



This idea "Tag note to a version" (to an espace) is much the same as "Check-in comments" from André Vieira back in 10 May 2010!

The only addition here is that you could add, or edit, the "Note" / "Check-in comment" after the publish has already been done, and I think that is not mentioned in "Check-in comments".

Maybe merge this idea with the other one?...

--Tiago Bernardo