"Created" and "Modified" dates not set properly on item duplication

Hi folks,

This specific "item specification" has not been changed for several years and I believe it goes back as far as 1Password 4. If one of the 1Password apps were not following this, it would be a bug in that version. That's part of the reason we're doing this new 1Password Core project, to use a unified codebase that follows the same specs across all platforms and also why we chose to rename this from Copy to Duplicate to better reflect its use.

BobW,

How are people out there using the duplicate feature? If they're using it because they want to create a second, archive-quality copy of an item that retains cross-item audit-ability, then this approach makes sense.

The most common use case is to duplicate the item into another vault they're sharing with friends, family members or teammates. So, it is meant to be a "duplicate" of the same item with the same timestamps. It's not meant to be used as a "template clone" in this case, even though we are aware of this use case and have even recommended this.

For that specific use case, we do want to bring our custom template feature out of beta that's available in 1Password for Teams/Business to everyone but we don't have an ETA on this.

Another reason to keep the same timestamps is that Watchtower depends on this data as well; to indicate when a password hasn't been changed for an example. So if you share an item that has no password history but has a password, the CreatedAt timestamp is used to calculate when the password was created or last modified; which is where our Watchtower's Compromised Logins feature kicks in. If we duplicate to another vault and change the timestamps, then it would throw off the audits and folks may not know they are using a compromised Login item.

We do want to look for a different approach for this as well.