I second this longstanding request. It's all good and well that certain fields should be filled and checked for database consistency when an item's category is changed. but that should be easy to flag - copy the existing stuff into a general (e.g. notes) field and show the fields that should be set up properly.
Btw., have you tried using the "create a new item" e.g. in the passport category? The fields requested there are relevant, but tedious. I tried to set my birthdate. It shows a calendar of the current month (July 2024) and the only way to get to my birthday is 77 years x 12 months = 924 clicks on the back arrow! You can't be serious! I entered the birthdate as a text field. So much for keeping the database consistent, Mr. Developer.
I like the way 1Password has expanded the Categories available. I also like that when setting up new records, one can choose and existing Category \"template\". To make using easier, I'd like to change the Category for an existing record from one Category to another without changing the data structure that exists. Is that possible please?
\n\n1Password Version: 8.8.0
\nExtension Version: 2.3.7
\nOS Version: Windows 10
\nBrowser:_ Chrome
I like the way 1Password has expanded the Categories available. I also like that when setting up new records, one can choose and existing Category \"template\". To make using easier, I'd like to change the Category for an existing record from one Category to another without changing the data structure that exists. Is that possible please?
\n\n1Password Version: 8.8.0
\nExtension Version: 2.3.7
\nOS Version: Windows 10
\nBrowser:_ Chrome
I second this longstanding request. It's all good and well that certain fields should be filled and checked for database consistency when an item's category is changed. but that should be easy to flag - copy the existing stuff into a general (e.g. notes) field and show the fields that should be set up properly.
\nBtw., have you tried using the \"create a new item\" e.g. in the passport category? The fields requested there are relevant, but tedious. I tried to set my birthdate. It shows a calendar of the current month (July 2024) and the only way to get to my birthday is 77 years x 12 months = 924 clicks on the back arrow! You can't be serious! I entered the birthdate as a text field. So much for keeping the database consistent, Mr. Developer.
I second this longstanding request. It's all good and well that certain fields should be filled and checked for database consistency when an item's category is changed. but that should be easy to flag - copy the existing stuff into a general (e.g. notes) field and show the fields that should be set up properly.
\nBtw., have you tried using the \"create a new item\" e.g. in the passport category? The fields requested there are relevant, but tedious. I tried to set my birthdate. It shows a calendar of the current month (July 2024) and the only way to get to my birthday is 77 years x 12 months = 924 clicks on the back arrow! You can't be serious! I entered the birthdate as a text field. So much for keeping the database consistent, Mr. Developer.
