Marge items feature?

Hello @amfarbs! 👋

Thank you for the suggestion! We do have an open feature request for a tool that would allow users to merge items and, while I can't make any promises, I've added your vote there so that our product team is aware that this is something that you'd like to see.

Can you tell me a little more about how your personally ended up with items that you would like to merge? Our product team would like to know more about the nature of the duplicate items so that we can improve the situation here.

-Dave

ref: PSS-I-25

I just switched my family over from LastPass and am running into the same trouble. LastPass had some sort of convoluted feature that was called something like "consider as the same website," (I can't see it anymore because I just nuked my account after migrating here,) and it just linked subtly different addresses, external to an individual login entry- basically the same as 1Password's feature allowing a single logon to contain multiple websites. (I think your approach is simpler and makes more sense, but it needs to be automated.) LastPass however was able to do it automatically. I didn't even know their feature existed until I stumbled on it in their settings one day. Because I didn't need to know about it because it made my experience just work.

It's a pain for me, who is tech savvy, to go through ALL my Chase Bank logins for example, (https://secure01a.chase.com/web/auth/logonbox, https://secure01b.chase.com/web/auth/, https://secure03b.chase.com/web/auth/, https://secure05a.chase.com/web/auth/, https://secure05b.chase.com/, https://secure06ea.chase.com/web/auth/logonbox, etc...) and manually perform a SEVEN step process to move EACH website to just one Chase login entry. I have precisely 50 Chase login entries in 1Password at this time. That's 350 clicks just for ONE incredibly common and mainstream website. To ask my 73 year old mother to do this is utterly impossible. It's also far from easy for her to understand that if the first Chase login offered to her by 1Password doesn't work, that another, of maybe dozens, will likely work.

Forgive me if I sound a bit snarky. I just read a dozen separate threads in this forum going back 9 YEARS with many responses from your team disingenuously suggesting that this is an edge case that almost no one encounters and therefore not likely to be prioritized. Heck, so many major websites like Facebook have many different prefixes, as in http://www.facebook.com vs m.facebook.com, etc. This is a BASIC component of how websites function, and has been for decades. It's absurd that 1Password would consider each of those a separate login and provide no way for users to combine them swiftly, let alone handle it automatically in the background. At the very least, it should be supremely simple to add a manual user-triggered tool that allows me to select all my Chase entries at once, right-click, and then select Merge Websites Into One Login Entry. If there's any conflicting usernames, passwords, or more, just dump it all into the Notes field as appended data.

Please prioritize this entire problem.

@kjdiehl

Welcome to 1Password! 🙂

If you've included https://www.facebook.com in your Login Item for Facebook then 1Password in the browser will, by default, offer to fill your Facebook login on both facebook.com and m.facebook.com. You don't need to add all the different subdomains to your Login Item individually.

The same thing goes for your Chase Bank example, you only need to add https://www.chase.com and 1Password in the browser will offer to fill on all of the subdomains. Are you seeing different behaviour on your end when you create a Login Item for Facebook and add https://www.facebook.com as the website URL?

-Dave

I would like this, too.

@Lorraine_

Thank you for the feedback.

-Dave