display tags better

philmcole

Hello,

currently in 1Password 4 for Mac when you view an login item, you can't see all tags. If the tags are longer than the space from left to right, they become hidden. To see all the tags that are attached to one item, you need to go into the editing mode, jump in the tag field with your courser, and navigate with the arrow keys to the right or left.
For me this is not comfortable. I usually attach multiple tags to one item and if I want to check back on an item, which tags are on it, I want to see them at first glance.

For demonstration I created a login item named "Test" and attached three long tags to it:
"Testingtesting1" "Thisisthesecond" "Andhereisnumber3".
As you can see in the images attached below, in normal view you can see only the latest two, but the first tag is cut of.
When you switch to the editing mode, and navigate with the arrow keys as explained above, you can see the first tag too.

Can you please change that, so that the tag box doesn't get cut off. It reminds me on viewing text in notepad on Windows and you forget to check "line break" and all your text is one long line through which you need to scroll.
My idea would be, that you make the tag field like a box, which expands dynamically, depending how long the tags are. Similar as when you turn on "line break" in notepad.

Many greetings and keep up your good work!

chrisdj

Hi @philmcole‌,

I see what you mean. I will file that for the developers to check out and see if we can get that to wrap down instead of cutting off. :)

Thanks for taking the time to let us know!

ref: OPM-1980

philmcole

still no change.. why can't you fix such a tiny little detail? It's really annoying.
Love your app and your work, but you make sometimes promises which you don't keep.

robbski

"...but you make sometimes promises which you don't keep." I beg to differ. chrisdj did NOT say he was going to immediately change the software just for you! I'm sure this request has been filed with Agile's software development team. If they implemented everybody's requests to change 1Password to suit their needs, there would be a new version of 1Password released everyday for who knows how many years!

Megan

Hi @philmcole‌

I sincerely apologize that you're still running into this bug. You'll notice that at the bottom of Chris' post is a reference number - the issue has indeed been filed with our developers. New versions mean a lot of little details for our devs to polish up, as well as a whole list of new features that didn't quite make it into the 5.0 version, so there's a lot to keep them occupied right now. I'd be happy to mention to them that you're hoping to see a resolution to this issue soon, but unfortunately, I can't promise that this is something that will be resolved by the next update.

We really appreciate your patience as we work to polish up 1Password 5! :)

philmcole

It's very nice, that you response fast and kindly.

But it's now already two months later, even almost four after the initial post of mine, and you couldn't get a feature that tiny into the programm.
Version 5 of 1Password is out for some time and I really like it. What I just can't understand is, that you are not able to implement such a little and small change. You can't tell me, that this is so difficult. I keep feeling, that you don't pay attention to older and smaller bugs, that are not that important. But for a really good programm it's important to polish also the rough edges and not only to implement new features.
It's such a little detail and I'm sure it won't take much work to fix it, so I hope you'll bring an update actually some time soon.

AlexHoffmann

Hi @philmcole‌,

We want to thank you for being so passionate about making 1Password an amazing product. Believe me when I tell you that all of us here at AgileBits feel the same way.
Every change, even if it appears small, can have major impacts. Because of this changes, like the one you're fighting for, aren't always as easy to implement as one might think.

I am going to ask one of our developers to take a closer look at this and get back to you here.

Cheers and Happy Holidays!

Rad

Hi @philmcole,

Thanks for taking the time to write to us and for following up on this issue :smile:

@AlexHoffmann, asked me to take a look at your issue and I totally understand the way you feel. I just noticed that this bug is already “planned” (scheduled), which means that we’ll squash it really soon. YAY!

However, I cannot give you an exact timeframe of when it will be fixed, but I can assure you that it will be addressed in the very near future.

Cheers and Happy Holidays!

ref: OPM-727

philmcole

Damn, still not fixed. Its 6 months now, half a year. I will probably never understand, how such a tiny detail can't be fixed in that time. Have I already mentioned, that it is annoying every day? That I have to go into "edit mode" every time, just to see all the tags? Yeaaah, has all been said earlier.
Jeez.

rickfillion

Hi @philmcole,

I understand your frustration, and I'd like to apologize for your expectations not being met. Especially since in december (on christmas day, no less) we told you it'd be squashed soon. The reality is that this hasn't been looked at since then. There's a triage process that happens with bugs, it makes the more critical ones float to the top to get resolved first. For example, crashes tend to get top priority because... well... obviously no one should have to put up with crashes. Next up is Regressions, which is any features or functionality that once worked, but somehow got broken unintentionally (we never want to break old when adding anything new, but it happens every now and again). Those two categories are what typically make up our critical fix list for a release. We then go and find a bunch of other bugs to add to the release to be fixed. Everyone has their pet bugs they want to see fixed.

No one disagrees with you that this is a bug. We should do better here. It's just a matter of finding the time to do it. Looking at this bug (OPM-727) in particular, it looks like we've had the intention of fixing it in several releases. But because it's a relatively minor bug, it looks like we aren't getting to it in time, and it gets pushed over to the next release.

I hope that we can make this up to you with a future release that has this issue resolved.

Rick

philmcole

Just wanted to remind you again. Maybe you'll manage to fix this tiny bug before September 2015, when it would be one year since my initial post. Wouldn't that be a goal?

Drew_AG

Hi @philmcole,

Thanks for checking in again. I'm sorry it's taken so long, but you'll be happy to know that this was actually already fixed in a recent beta of 1Password 5 for Mac. Barring any unforeseen circumstances, the fix should be in the next stable release update, although I don't know exactly when to expect that. But there's definitely a "light at the end of the tunnel" now! :)

Thanks again for all your patience!

ref: OPM-727