Looks like this thread has been here for a while. I haven’t read ALL 189 posts, but from the jest of it, a lot of people would like more types added, me included. I am coming from an app that has all sorts of types, and I’m now finding out that I have to squeeze most of them into the Secure Note and customize the fields to fit. Taking some work, but I will make it work.
I’ve cast my vote to add additional types.
Hi @rosede, you’ll be happy to know that ‘additional item types’ is included in the 2022 roadmap.
This is great to hear. Thanks for bring it to my attention.
Hi Community! HI @Kruger2147 ! How are you guys?
Great idea… this is great. ^^ awesome… So… I have this idea.
- Here have some item types
- Item types are associated with item type by association. Example: Login inside => Type: “Common type item”
- I read all the comments and got this inspiration, I made this ui to represent everyone’s opinion here
- I’m happy if I can represent everyone’s idea here with this beautiful graphical interface ;D
- I hope to help
This looks awesome! I hope these options are added to Bitwarden in the near future
Update from the product team: additional item types are in early development, beginning with a significant refactor of how item types are stored in the database while keeping the product backwards-compatible. This will also enable faster creation of new item types. Making progress!
Could you tell us what item types are being added?
If this is still in early development, how could they possibly confirm this, @Korat?
WEB SITE LINKS SAVING. Nowdays we visit so many websites to read and forgot too. Usually Passwords are related to websites. Not all websites have password request. Saving websites links are very useful. Please consider adding this too.
I’d really love to use additional items.
I’ve always wished to have a Software Licence Key Item
(Developer, Software, Version Number, Key, Activation Date, Expiring Date etc.)
and a contact item to use Bitwarden as address book.
Less fields than the identidy item but importable from *.contact *.vcf *. files or via scanning a QR code.
In Addition to that my insurance company sent me an digital insurance card today to add to a digital wallet via QR code (my insurance company recommendet the app “PassWallet” from Google Play Store.
My first thought was: It would be nice to considure Bitwarden as this digital wallet.
This cards have to be importable via scanning QR code.
I’ve uploaded a screenshot of this PassWallet entry in Google Play, here is the link:
I have the same question about year later…
These types are available only on Premise or something?
I tried to found more types, but without results. I have premium account…
Hey @iAmMember additional item types are on the roadmap, stay tuned!
Hey @dwbit thanks for ansawer!
Looking forward! Additional item types are for me now the most needful option in Bitwarden so i will waiting impatient for it
I paid for a year of a Bitwarden family account to bake it off against my 1Password. Let me preface, I strongly, strongly dislike 1Password: Their customer service is unfriendly and arrogant. The pricing is borderline predatory, and how they’ve treated customers who purchased perpetual licenses is abhorrent.
After coming across this thread, and seeing a request that is…
– Four years old, to design, implement and deploy new database models plus the necessary front-end refactor work is confusing. Looking at Bitwarden’s GitHub release cadence, there are consistent patch releases, and semi-regular dot releases. I understand as a small company that scope is hard to manage, but with an open source community that is eager to contribute, why not encourage the community to contribute to larger changes like this? I have a blanket assumption in my head the average BW user is more technically adept than most, understands OSS, and would probably be happy to contribute on larger workstreams like this request, if some direction was given from BW on the help it needs/wants to get these requests over the finish line.
– Indicative of a pattern that plainly ignores community feedback (Feature Requests - Bitwarden Community Forums). As an outsider, it feels like a lack of customer empathy and lack of resourcing to working on the core product could be an issue. (The GitHub releases page shows many enterprise and saas related functionality being implemented for the server repo).
…I’m going to very sadly stick with 1Password when it comes time to renew my BW or 1P accounts. I love Open Source software. Personally, OSS is what pays my salary, so I feel uncomfortable making this pointed criticism towards this product that is well-intentioned, but just doesn’t deliver on basic needs. I’d pay 2x the cost of my 1P subscription to move to an OSS product that has a decent saas offering. If I can’t use the product as myself, and others want to use this product, then I’m going to move away, and stop patiently waiting and hoping with fingers crossed that the folks who decide the roadmap will eventually organize work towards what customers are asking for.
I hear you @classicwebdog, but I do think it is unfair to directly compare a $7 Billion dollar company with literally hundreds on their development team to Bitwarden, the new guy on the block, who is a small startup with a dozen or two developers and has only been around for a handful of years. To suggest that Bitwarden ignores their customer base is grossly misguided, in my opinion. They just haven’t built up their company yet, so you really can’t expect them to be as agile or responsive as one of the huge and established players like 1Password. But they are doing more and more every month. I’m very happy about that, and despite their small size, I think they offer a better product, a better service, and better support than 1Password, which I used before Bitwarden.
And PS: additional item types are in the works right now and coming soon. See the BW roadmap.
Thanks for the feedback @classicwebdog, while additional item types is on the current roadmap, I would also invite you to come and chat with us on June 23rd for the Bitwarden Community Forum.
We will be covering what goes into making the Bitwarden roadmap, but it is also an open forum to hear from you, so bring any questions and concerns to chat about with fellow users and the Bitwarden team.
I’m also glad to hear, that more item types are on the roadmap. I’ve migrated from 1Password to Enpass and now to Bitwarden (Premium + organisation for family sharing and files). At the moment, it feels a bit less comfortable than Enpass, because I miss also types, for my licenses, bank accounts, Linux logins (like passphrases for encrypted disks) etc. pp. I have to put most of them into “Secure notes” …
It is just in the past year or two that Bitwarden has been in a position to be able to add additional DevOps. And honestly, the developement cycles and feature additions in that time have been staggeringly increased! Just look back at the release notes and compare that to the GitHub project commits (for server) prior to 1-2 years ago.
Prior to that it was literally one guy (Kyle Spearrin) and whatever the community decided to pitch in on. It is absolutely wonderful that Bitwarden has grown into a status of “seems just like 1Password as a company”, but the fact is that 1Password (Initial release June 18, 2006) has been in development for a lot longer than Bitwarden (Initial release August 10, 2016) and has had a huge staff for DevOps for many many years.
Bitwarden is playing catch-up on many features and has to prioritize things based on many factors. They have already caught up in many ways, which is why they seem like they are in the same class as the big established players already. Give em some time and latitude and I imagine they will catch up and surpass on other features as well.
Edit: Typos and additional context.