Why this doesn't work?

@Fran​ That's why this option exist to keep old name on old credits or not, because sometimes name is just incorrect and you need to change it, doesn't matter it's old credits or new credits, but this option just doesn't work
You still need to correct credits doesn't matter you change name or not

If a name correction with "preserve previous name" disabled cannot be approved as is, it might be better to decline it rather than approve it with "preserve previous name" enabled. Then the contributor would have the chance to add better justification.

It never approves it
Always 100/100 times same result
Why then this option exist if you still have to do same work?
Just now twice

@ugnieska​ 

Post the reference numbers, at least.

I don't do this feature now
Because it's useless
Just gives you more unnecessary work

Hello all,

Thank you for reporting this issue. I've forwarded this information to the appropriate team for further investigation. I'll reply once we receive further information. Thank you for your patience.

Can you guys help me posting some examples when this is not working? screenshots when is not working as it is suppose to, so we can take a look! 

@Fran​ I cannot recall even the name pages I've merged or corrected where this was a thing, let alone provide a screenshot I'm afraid.

I can however say, every time I've done this, bar one time it worked as it should, no matter the evidence or explanation, an attribute was created for every credit. I even had a staff member do a merge for me once after I was denied and it happened.

Now I use work arounds, if there's few credits, I move them to the correct page and merge the empty page into it, or if it's a correction, I use screenshots as evidence and add attributes to all the applicable credits, then when the page name is changed, those disappear and no wrong ones are created, a pre-emptive strike if you will.

I will try to not do that next time I merge or correct a namepage to see if I can have the problem occur and post it here.

Anyone reading that has this issue happen lately or in due time should also post it in here.