3 Feature Requests: Merge, Add Web Forms, Public Feature Request tracking

kazooless

1. I found an old thread when the latest version was v4. It said that v3 used to have the ability to add a web form item when editing and for some reason you removed that from v4. It looks like it still doesn't exist in v5. No clue why you would remove features, but this would be really helpful to have again. The lack of it cause me to have to go through a bunch of extra hoops to correct a mistake when creating a login item for a new website.

2. In the same line of editing items, it would also be extremely useful to be able to merge two login items together. Sometimes 1Password doesn't recognize that a new page is from the same site and therefore it doesn't let you update a login, but only create a new one. Merging would save a LOT of work.

3. There seem to be a lot of usability feature requests. There are sites out there that let people make requests and then add their votes to them. See this for example: https://kace.uservoice.com/forums/82699-k1000 Please consider using something like this.

Ben

Hi @kazooless‌

I found an old thread when the latest version was v4. It said that v3 used to have the ability to add a web form item when editing and for some reason you removed that from v4. It looks like it still doesn't exist in v5. No clue why you would remove features, but this would be really helpful to have again. The lack of it cause me to have to go through a bunch of extra hoops to correct a mistake when creating a login item for a new website.

A "web form item"? Could you please elaborate? Or perhaps link to the thread in question?

In the same line of editing items, it would also be extremely useful to be able to merge two login items together. Sometimes 1Password doesn't recognize that a new page is from the same site and therefore it doesn't let you update a login, but only create a new one. Merging would save a LOT of work.

Agreed. Great idea. I've filed a request with our developers for their consideration on this.

There seem to be a lot of usability feature requests. There are sites out there that let people make requests and then add their votes to them. See this for example: https://kace.uservoice.com/forums/82699-k1000 Please consider using something like this.

We currently track (many) feature requests in our bug tracker, which is not public. In order to accommodate this we would need to switch to a different system for feature requests (whereby they are less likely to be seen by the eyes that need to see them). Solving one problem may cause another here.

kazooless

This should answer your question...

littlebobbytables

Hi @kazooless‌

Just to say, we didn't remove the feature but as version 4 was a complete rewrite of the code we just haven't had time to bring it back yet. It has been requested though. I've never quite understood the advantage of being able to add arbitrary fields to the web form details section given it would mean the user needs to pour through a pages source code for IDs. Still, your request is noted (and you have company in it too).

kazooless

@littlbobbytables I think the need/desire for it would be mostly alleviated by the other request: merging. I'll give you a scenario where it popped up for us:

We decided to move to a new bank, an online bank, Capital One 360. I opened 4 user accounts, two are joint with my wife, and the other two were new checking accounts for my college sons. I was teaching them how to use 1password. During the create an account process, 1pw asks if you want to save the new information when you create the username and generate a password and confirm password. So far so good. Then it asks you to fill out 5 questions and answers. Using your sites suggestions, we generated those answers too and then 1pw asks if we want to create a new login or update an existing. When we updated the existing, it messed it all up and took a lot of editing and using the previous password deal in order to fix it. But we couldn't 100% fix it because we can't create a new item there. Moving on...

The next time (for a new account) we created a second login item. This time, the questions are all in there. But we don't want two items for the one site. Merging these two, with the ability to edit the merge before completing it, would fix a lot of this. But we also could copy and paste to merge. But wait, we can't create a new item, so that doesn't work either.

The best we could come up with was to add the URL's and username and password to the 2nd item and delete the first. But it is all a pain point and could work a lot better.

Thanks for listening. Hopefully this will help the designers...

MikeT

Hi @kazooless,

then 1pw asks if we want to create a new login or update an existing. When we updated the existing, it messed it all up and took a lot of editing and using the previous password deal in order to fix it. But we couldn't 100% fix it because we can't create a new item there. Moving on...

Yea, that's generally because 1Password thinks you're updating the password. It doesn't know how security questions/answer works, only that there is a password field on the site it needs to save.

What we recommend instead is to anchor your Login item for the site, so it stays on top and you can edit it. Here's a video to show what I mean:

Keep in mind that 1Password cannot fill your second account data if you put it in the first Login item, each account must be a separate Login item for 1Password to be able to fill in the data when you request it.

ryanfitzer

@littlebobbytables‌,

I've never quite understood the advantage of being able to add arbitrary fields to the web form details section given it would mean the user needs to pour through a pages source code for IDs

My need for this feature is that 1Password is not saving the state of a selected <input type="radio">. In the following screenshot, the radio with the label "This is a private computer" should be selected.

Since I know the input's name and value, it would be nice if I could just add it.

rickfillion

Hi @ryanfitzer‌,

Yeah, I can certainly think of cases where it would be really handy. Even if only used by advanced users, it would really be nice for this to be exposed again.

Rick