Hello, nerds!
Just a quickie update on what we've gotten done so far in the upcoming v5 (currently on the develop branch). Lots of stuff is changed under the hood, as we've upgraded the underlying framework to Laravel 5.7, but there are a bunch of bufixes and new features, as well as some UI improvements.
One of the bigger changes to the system is the introduction of Flysystem support, which means you can host your asset uploads, logos, etc on S3 or Rackspace.
The small things matter as much to us as the big ones do, so we've spent some time trying to really refine some of the commonly used UI elements, for example the improved logo upload+preview interface:

upgrade.phpnext_audit_date if none providedsamaccountname on LDAP importWe're currently working on a way to easily create multiple assets from the Create Asset screen. This is a little tricksier than it seems, because there are both front end and backend considerations (validation, etc), but it's coming along well.

I'm not actually sure how to handle this one right now, but backups will no longer work the same way with Flysystem. Need to investigate.
We're still shooting to get as many of the v5 milestone issues handled prior to release, but as always, it should be used as a roadmap guide, and some features/fixes many not make it in this version.
Hi I'm Kalpa De Silva from Sri Lanka working as a IT specialist from Large scale apparel business. I go through your all conversations and finally I installed on premise Snipe-IT system. I would like to give some major changes to your system and we already trying to do it using our internal
@thanukalpa If you have feature requests you're interested in working on, please see the contributing documentation, and make sure you discuss your approach with us here via Github Issue so that we can make sure you're going down a path that will work long-term for the project. Thanks!
Question, will the upgrade to version 5 from the latest stable likely be straight forward or should I look at installing the development version now and upgrade that to stable once it's released?
I know development should never be expected to be stable etc etc, but sometimes dealing with slight issues is easier than ripping it all out when it comes to upgrade time.
It should be pretty straightforward. The only thing that might take some shenanigans is if you decide to host your uploaded assets in AWS S3 or Rackspace separate from your Snipe-IT instance. We have a command line tool for that as well. Some directories will also be moved around a little, but the upgrade script should hopefully handle that for you without too much fuss. Hopefully. ;)
Thanks, I'll start with stable and wait a bit for any upgrade issues to be resolved (if there are any).
The link above for Migrating Files doesn't work, it takes me the documentation page with 404 page not found
@ichayapet v5 isn't out yet.
Are there any Plans to add Purchase Orders, like it was suggested in #6133?
Thanks for the great work so far!
Is this (#5854) commit about altering assets location through audits only coming with v5? Or is it the newest release?
@aaronpierce I believe that's only on develop right now so it will be in v5
In the develop preview, the bulk audit feature doesn't update locations if assets are checked out. What would be great is if you opened an audit, scanned all of the items, and then save (to continue to work on it later) or close (done with audit, ready to review) and review items that are checked out and select what to do with them (check out to new location, ignore, set status etc), remove items from the audit, and view what was supposed to be in each room and is missing, misplaced etc
i can't wait, thanks for the great work
wonderful!
@memtech3 - please open a new issue for that so we can discuss it there. Thanks!
@aaronpierce v5 only, sorry. It's too difficult to keep back porting features and working on the new version as well.
Will we get SSO/ Single Sign on feature in v5 release.
And u2f? Please allow security keys as 2fa.
@BharathKumarGajula @ffuentes alas, SSO and u2f will not be in the v5 release.
Hi @snipe, ok I understand. Can at least be addressed #6567?
When would be version 5 is available for public release, we are waiting for this release from long time.
How about Bulk Check In feature?
Is this still relevant? We haven't heard from anyone in a bit. If so, please comment with any updates or additional detail.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Don't take it personally, we just need to keep a handle on things. Thank you for your contributions!
Hi,
Will Maintenance Agreement/ General Agreements option included in this release? It would be great feature to have if its possible.
Okay, it looks like this issue or feature request might still be important. We'll re-open it for now. Thank you for letting us know!
Is there anything more to update on this? I know the versions of 4.7 had been released but was wondering when we could expect v5.
Hi, When we can expect stable release of v5?
Looks exciting! Can we also expect kits #6756 to make it into master for v5?
Are you guys working on something like #5081 forV5?
Is V5 ever coming out? Multi add assets and printing of equipment receipts are crucial.
Any chance of Snipe-IT v5 getting bumped to Laravel 6.0 LTS when it releases, instead of 5.7?
I'm ignorant of what that entails but LTS support sounds nice.
Laravel News
The Laravel team is proud to announce the release of Laravel 6 and it’s now available to everyone.
Is V5 ever coming out? Multi add assets and printing of equipment receipts are crucial.
yeah, i cannot deploy this solution without this feature.
I tried to look at what issues remained open, in case I could do some small part to get it live by contributing a pull request... I found five open issues on the v5 milestone, but the couple I clicked into had already been merged, so I couldn't tell if they were genuinely still open.
What can we do to help get v5 across the finish line?
Hi @phatuous - right now we're held up by testing, since the LDAP/AD integration is completely rewritten in v5, and we have to confirm that it will continue to work as expected on existing installations. So, testing is mostly what we need. :)
Ok - well we're definitely interested in the LDAP/AD piece, so that's a great fit for us to pitch in on.
how can we help with testing? we just finished setting up our own Test AD, so we've got a safe sandbox to play with.
@phatuous LDAP/AD login, syncing, etc. It should behave the same on both versions. Should.
roger that - we'll get cracking on standing up a parallel v5 version of our current V4.7.5 instance, and start hammering on the LDAP/AD piece. we'll report back any issues, esp. unexpected differences (we're expecting some intentional differences, like syncing of Department).
qq: should we be testing against dev branch or v5.0.0-beta-2 label?
develop branch please :)
Hello! Do you guys still need a hand to write tests? I am currently creating them here. I rely on ChromeDriver since phantomjs just does not work on my environment.
Is this still relevant? We haven't heard from anyone in a bit. If so, please comment with any updates or additional detail.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Don't take it personally, we just need to keep a handle on things. Thank you for your contributions!
@stale this issue is still relevant until v5 is released. @snipe can we make the stale bot ignore this issue somehow?
Okay, it looks like this issue or feature request might still be important. We'll re-open it for now. Thank you for letting us know!
Hi, seems LDAP Sync functionality is out in the wild on 5.0? #6352 brought in a lot of changes, but broke \App\Console\Commands\LdapSync as well as the sync via webui by removing \App\Models\Ldap . Copying the \App\Models\Ldap from the latest master, for now, seems to work, but I'm sure it's intended. Any pointers on what needs to be refactored?
Hi, seems LDAP Sync functionality is out in the wild on 5.0?
it's already present
@snipe do we have an ETA on a V5 release? Can we expect to see it at some point next year?
Hi !
I just want to know if you still need help on testing ? Anything we can do to help ?
Any ETA on V5 @snipe
Any chance that https://github.com/snipe/snipe-it/issues/5925 is going to make an appearance in V5?
It would be really helpful if multi-assets allows to input assets in a "comma separated" way instead of having to click.
Having a way to create multiple numerical based assets would be great too. i.e: using "MyDevice %[10-15]" to get MyDevice 10, MyDevice 11, ..., MyDevice 15 created.
Is this still relevant? We haven't heard from anyone in a bit. If so, please comment with any updates or additional detail.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Don't take it personally, we just need to keep a handle on things. Thank you for your contributions!
v5 is pretty relevant. @snipe Can the stale bot be backed off a bit, perhaps to four or six months?
Okay, it looks like this issue or feature request might still be important. We'll re-open it for now. Thank you for letting us know!
(bump)
issue to track LDAP changes:
Any status update when the release will be?
I would like to test the RFID integration, please can you let me know when this feature will be ready for testing?
@daletnt Can you be more specific about what you're trying to do exactly?
Heads up - we're shooting for an RC this week or next, with the aim to be to release v5 mid Sept.

Good to hear that it is going to be finally out...馃憤
top!
v5-beta-3.0.0 is released - https://github.com/snipe/snipe-it/releases/tag/v5.0.0-beta-3.0
GitHub
New from v5.0.0-beta-2 to v5.0.0-beta-3 IMPORTANT: This version of Snipe-IT requires PHP 7.2 or greater Added Accessibility features already back ported to v4.9.x Merge user script already back po...
Most helpful comment
Is V5 ever coming out? Multi add assets and printing of equipment receipts are crucial.