View Issue Details

IDProjectCategoryView StatusLast Update
0000094TeraCopy(No Category)public2017-04-12 23:04
Status resolvedResolutionfixed 
Product Version3.0.8 
Target Version3.1Fixed in Version3.1 
Summary0000094: Keep both
DescriptionImho the option "Keep both" that is present in case of name collision should interest only a single file and not all files with the same name, since it exists the option to rename all copied and all target files
TagsNo tags attached.
OSWindows 10
OS Version64 bit




2017-03-17 19:13

reporter   ~0000063

I DON'T believe it should apply to one file. If I'm using TeraCopy to consolidate then sort files when I have multiple versions of the same files, for instance, photos with possibly different sizes but the same filename, I want Keep Both to apply to the entire batch.


2017-03-17 19:55

reporter   ~0000064

Ok, I don't agree: Keep both is a redundant button.
But as is the case, please, add the option to rename only single file: renaming file by file it's a missing feature. The only alternative is copying files with Explorer


2017-03-17 20:33

reporter   ~0000065

I'm curious Jamil,

If "Keep Both" was removed or adjusted in behavior, how would you copy a directory full of duplicate images to a container folder and have TeraCopy avoid name collision/overwrite and rename the duplicates in some sane way in the target directory?

I'm familiar with how Windows Explorer/File Viewer had/has a Keep Both function, and Keep Both is a simple concept. How is it redundant? I really don't know.


2017-03-18 02:00

reporter   ~0000066

It is redundant because you can choose "Rename all copied files" from "More" button.
You already have the option to manage collision requests for single files, indeed you have "Skip" and "Overwrite" buttons.
However, as you said, it is a problem when you have to copy many files. Maybe a behavior similar to Explorer is the solution.

Issue History

Date Modified Username Field Change
2017-03-16 10:40 Jamil New Issue
2017-03-17 19:13 t1gsp Note Added: 0000063
2017-03-17 19:55 Jamil Note Added: 0000064
2017-03-17 20:33 t1gsp Note Added: 0000065
2017-03-18 02:00 Jamil Note Added: 0000066
2017-04-11 11:29 CodeSector Status new => resolved
2017-04-11 11:29 CodeSector Resolution open => fixed
2017-04-12 23:04 CodeSector Fixed in Version => 3.1
2017-04-12 23:04 CodeSector Target Version => 3.1
2017-04-12 23:04 CodeSector OS Version 64 bit => 64 bit