Merge never switched to default approval

Question

I have a merge in my list that was proposed over two years ago but has never reached approval. One profile has red privacy, but my father is PM and gave approval when he proposed the merge. The other profile has open privacy, so I would have thought it would have reached default approval after 1 month. Yet the merge still shows no approval from that PMs end. The other PM is not active.

Is this a bug? Or maybe the other profile was only set to open privacy after the 30 days had elapsed? Do privacy level changes show in the changes log? Is there a way to force default approval?

Comments

According to this guideline, merges involving Private profiles can only be completed by a team member:

https://www.wikitree.com/wiki/Help:Matching_and_Merging_FAQ#What_can_you_do_if_you.27re_waiting_for_approval_from_someone_else.3F

I would presume that the trusted list member(s) of the locked profile(s) could also complete the merge (but I could be incorrect).

I don't think it is a bug; it is a function of our privacy levels (again, I could be incorrect).

---

Ah, okay. Maybe it's not a bug, then, but if not it seems to me a design flaw. If the PM of the private profile has granted approval, and the duplicate profile is open, I don't see why a team member would need to be involved.

---

Because one profile is private, no one else can see the information and cannot 'update' the profile, which is what is done during a merge.  Send a message to info @ wikitree.com with the profile that needs merging and they can complete the merge OR have your father complete it, if he is still PM of the locked profile.  Depending on the dates on that profile and if it is a living person, he could also 'unlock' the profile, which would allow anyone to complete the merge.

---

Barry, i believe your Dad could complete that merge, since he is manager for the private profile. Has he tried?

Answer 1

Yeah, I have one also. Roberts-8417

Answer 2

If I'm not mistaken, its a bug that happens from time to time.

It could be that the privacy level prevents default approval.

The only way I know to get around it (unless an admin can fix it), is to reject the merge, and re-propose it -- which restarts the 30 clock for default approval.

Comments

I believe that as long as one of the profiles is locked, you can't "get around it" by rejecting and re-proposing the merge.

Locked is locked - you need to be on the trusted list of the locked profile(s) to complete the merge, or request assistance from "the team".

Answer 3

I expect it's privacy.  But should it be?

If I'm the PM on a Red profile and I propose a merge with an Open profile, and I get no response, and it doesn't default-approve, then I'm a bit stuck.

Comments

Then you use the Unresponsive Profile Managers system.

However, my experience has been that the locked profile (Red Lock, at least) may be deleted, rather than opened to a non-current-trusted-list member.