Move Detection across Folder Pairs

[henning74]

Dear Zenju, please consider supporting the detection of moved files across multiple folder pairs within the same job.

Within one job, multiple folder pairs can be defined. I found out that in version 8.5 the movement of files that have been moved across folder pairs is not detected.

I have a use case that looks like this: projects/p1; projects/p2; projects/p3; [...] projects/pN
My job contains the folders: projects/p1; projects/p3
Movements of files happen (newly) between p3 and p1.

I could workaround by regression to having only one folder pair (local/projects <-> remote/projects) with the filter \p1\*; \p2\*
However, by this workaround I have the same functionality and appearance as when one job could only handle one folder pair. The main advantages of multiple folder pairs are though, as I see them, to make multiple folder pairs explicit rather than typing them into the filter, and to separate both definitions from each other, both of which I appreciated in the past. Thus my above request.

Thanks in advance and best regards

[henning74]

*push*
Is my proposal considerable?
Regards

[Zenju]

Technically this is not possible with the current design which works by processing each folder pair one at a time. Also for cross-folder pair move detection it is required that all folder pairs involved are set up to create database files. However there seems to be the simple workaround of using a single folder pair for the parent folder in combination with an "include filter" that includes the individual child folders.