Should we not to carry-over a status field value when duplicating a record?

[yuri]

Should we not to carry-over a status field value when duplicating a record? But leave it default.

Use case. When we duplicate a completed Meeting, in most cases we wouldn't need the status to be 'Completed'. Should we have such a logic for all entity types?

[item]

Hi,
i have vote "Set the status to default"...
I see other vote "Carry-over the status from a duplicated record" but if explain why, we can understand

So maybe :
"duplicate" or "clone"

And what about "duplicate checker" ? Clone can bypass duplicate checker ?

Brainstorming

Yuri, very nice idea this post


EDIT : https://forum.espocrm.com/forum/deve...3-clone-entity

[yuri]

Duplicate checking is applied for duplicates I believe, supposed to.

[bradaks]

We have clients that duplicate a custom entity for ease of creation. Status for us should always be set back to default as it is a new record that requires a new workflow to be complete.

[yuri]

Implemented https://github.com/espocrm/espocrm/issues/2885