Does anyone else think the way AEM handles versions is backwards?

[dmescia2]

If I drag a new version into AEM and select to save it as a new version then go to the timeline an dlook at the versions the original is labeled and New version 1.1 and the new version is listed as current. An end user will look at that and think that New Version 1.1 is the one they just uploaded. Can the original asset be listed as the orginal and then every new version is called new version 1.1, 1.2, etc. Current could just be an a status icon to the right of the version to show which version is the current one. Am I the only one that thinks this or is this a common complaint?

[Mike_CBA]

I agree, similar with our Workfront proofs, when dragging into the AEM Assets (DAM) folder it automatically creates a subsequent version - which seems ridiculous from a version tracking POV, when questioned if we could change this the response was that's the way the system is designed & built - TBF this has not yet created an issue (yet) - however as we scale both AEM DAM & WKFT across the business it would be something we'd want to uplift so that the proof version that's approved is the same version count as the asset uploaded to AEM....  

I'll keep an eye on this ticket to see if you get any traction/suggestions - cheers

[dmescia2]

AEM should learn from Workfront on how to handle versions. I'd recommend you make a new asset when its finalized to put in the DAM. No need to keep all of those versions in there.