Hi 1P,
I started this thread many months ago now. I believe I have been very patient. As one person said further up, it's not really a feature request as it was a 'core' feature of a previous major version. If anything, V8 should not have been released until this was part of it. It is taking away core functionality and labelling re-implementation as a 'feature request'.
I, along with many people I know are very close to stopping using the product because of it. In 2023, there is all sorts of information that sits alongside a credential. All sorts of 'MFA recovery keys', all sorts of 'API keys' etc. etc. All of said information needs to be inside 1 object. The fact that these fields and sections can't be organised at all inside an object, more than a year after mainstream release is beyond shocking. I 'want' to start using V8, although I don't like some of the UX / UI design compared to V7, it 'has' however got a lot of improvements in terms of speed, reliability and so on. Here I am, 14 months after the release of V8 and I'm still stuck using V7. Which I might add, has a lot of issues in its own right. Especially when Iām forced to use V8 on mobile.
I understand 1P has taken a 'information close to your chest' stance on feature requests being implemented when it comes to dates and rollouts. However, this post / specific feature request is now many months old. Please, please provide more information than you currently have. If you are unable to provide a date or at least a rough date for this feature, I will be forced to leave 1Password and start using Keeper instead. Regardless of how large the migration job is. I will also have to start recommending the businesses and individuals I support (as an IT MSP / consultant) do the same.
This is very sad as I've used 1Password since its release many years ago, since it was a standalone app on iOS.
Please can you also remove the company name I stated in my original post. Maybe **** it out or something. Thanks.