I’m currently switching from the crappy LastPass to the highly acclaimed Bitwarden, and even though I probably won’t need it right now, I went ahead and ordered Premium as support. But I stopped the migration.
The custom templates in LastPass are terrible, but at least they exist. Since I couldn’t find any custom templates for items, I thought I wasn’t smart enough to find the feature.
ChatGPT then told me that this basic feature is not available and linked me to this thread.
I read through the thread and can’t believe that custom templates have been discussed for exactly SEVEN YEARS, have almost 31k views, and have the tag roadmap:planned.
My plan was to switch to Families after the migration. Without custom templating, that doesn’t make sense.
Before I start migrating about 1k records from LastPass to Bitwarden: When will the feature be available? Is the feature assigned to a fixed version? Is help needed?
Thank you for your message. But I did not mention “fields” at all. My post is about templates
Stage 1: Custom templates (e.g. for API-Tokens) / my post
Stage 2: +Templates provided and maintained by BITWARDEN
Stage 3: +Templates provided and maintained by Community Members
Stage 4a: +just copy and paste everything and OpenRouter and the preferred LLM does the rest
Stage 4b: +just copy and paste everything and OpenRouter and a pretrained agent of the preferred LLM does the rest
@AJD_bn Even though you are using the term “custom templates”, it sounds like you might actually be asking for an increased variety of pre-defined item types. Please confirm whether this is accurate, in which case I can move your comments into the corresponding feature request topic.
To be clear, customizable vault templates (the topic of this feature request) are templates that users create by adding, deleting, and/or re-arranging various custom fields and standard fields (probably with an increased variety of standard fields available to choose from), and then save in a way that the template can be used as a basis for new vault items. The best available work-around for customizable vault templates at this time is the Clone function (i.e., create a vault item with the custom fields that you want, save it in a convenient location, and then clone it whenever you want to create a new vault item using the same structure).
I’m moving to Bitwarden from Dashlane because of a consistently degrading user experience.
However, one of the UI features I’ve really liked about Dashlane was how they collate and display specific ID Information.
As an example, a drivers license or passport will have multiple relevant fields specific to those IDs such as ID Number, Issue Date, Expiration Date, Class (for DL), Issuing Country/State etc.
I understand that I can add custom fields for this information but then it just becomes a block of text and disassociated from the identification fields further up the list.
Rather than having this information separated, and rather than having a single “Identification” block, it would be nice to have multiple “Identification” blocks specific to the ID which would present relevant fields.
@thebundok Welcome to the forum!
I have to confess I’m struggling a bit to understand your request. First, what do you mean by “block”, and where would these “blocks” be found?
Perhaps you’re using the word “block” to mean a vault item type (like Login, Note, Card, and Identity), so you would like to have available more specific versions of these (e.g., Identity-DriversLicense, Identity-Passport, etc.). If that is what you’re proposing, then there is actually an existing Feature Request on this topic:
My apologies for being confusing. I was referring to the blocks of information. i.e. “Contact Information” is one block. “Personal Details” is another block. What would you call them so I can use the proper terminology in the future?
In the “Identification” ‘block’ there are 3 pre-defined inputs: SSN, Passport # and License #. I was suggesting that it would be more helpful to have those as predefined blocks/sections rather than single line-items in one general “Identification” section.
In other words, a pre-defined section for Passport, which includes issuing country, passport number, issue date, expiration date etc. (I think the additional pre-defined fields is where it lines up with the existing Feature Request you posted).
Hope that makes more sense. So while it does have similarities to the existing feature request you linked to, I felt it was a bit more nuanced and justified a separate request.
Perhaps also allowing users to create their own custom sections, rather than only allowing custom fields, as well as the placement of those sections.
… I think your request also has some overlap with this other feature request: Customizable vault item templates (–> with customizable vault item templates, you could create your own “blocks” / templates, in a way…)
Ok, seems you agree that there is some overlap – would you say, your request and Customizable vault item templates are more or less the same request (“identical”)? Then I would merge your posts into this other request.
