Changes between Version 2 and Version 3 of Ticket #17866


Ignore:
Timestamp:
2019-07-01T16:30:51+02:00 (6 years ago)
Author:
skyper
Comment:

No undelete needed.

I add an example file.

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #17866

    • Property Summary Merging undeleted node: youngest instead of oldest id and history kept → Merging nodes: youngest instead of oldest id and history kept

  • Ticket #17866 – Description

    v2 v3  
    11==== What steps will reproduce the problem?
    2 1. Have an undeleted and another node with higher id than the first one
     21. Have an node and another node with higher id than the first one.(568979540, 3825090301)
    331. select them (order does not matter)
    441. merge them with menu function or keyboard shortcut 'm'
    … …  
    77Lowest Id and history of the oldest node is used/preserved.
    88==== What happens instead?
    9 Id and history of the node of the younger node is used.
     9Id and history of the younger node is used.
    1010
    1111==== Please provide any additional information below. Attach a screenshot if possible.
    1212Thought the order of selection did matter some time ago.
     13Strange, it seems to happen only on some sessions.
    1314
    1415{{{