github snipe/snipe-it v6.0.6
on GitHub

latest releases: v7.0.13, v7.0.12, v7.0.11...
2 years ago

This version includes some small bug fixes and a handful of UI improvements that we think you'll really love - and adds a new index to improve performance. We also snuck in some additional filters for several of the API endpoints, so you can now search on name, address, etc on things like locations, categories, companies, etc. (You could always search by name, address, etc but it would search across all fields instead of that specific filter field.) We'll be updating the docs shortly.

We've also made some improvements to our SCIM support so that it should be more tolerant of missing fields. We've love feedback on that either via Github or on our awesome Discord server. (Seriously though, the community there is great and you should definitely check it out.)

First, the good stuff:

Model Files Uploads

This is a feature that we know people have been asking for so we're excited to finally deliver it. Asset Models now allow file uploads, and will appear on the models page and also on the new "Additional Files" tab of the individual assets. This is great for things like user's manuals that you would have previously had to upload individually to alllllll of the assets within that Asset Model, which was a bit of a bummer, and a waste of time and disk space.

Screen Shot 2022-06-28 at 4 18 32 PM

Screen Shot 2022-06-28 at 4 19 42 PM

Custom Fields Weirdness

We've been seeing an issue in certain cases where PHP has been upgraded that can result in a 500 error when adding/updating an asset, because what we're expecting that column to be named (from the custom_fields table) and what it's actually named on the assets table are now different, due to (what we think is) a small change in the PHP transliteration library.

This updates the existing snipeit:regenerate-fieldnames console command to check both the column name on the assets table and also the value in the db_column field in the custom_fields table.

You can tell if this script will fix your issue by going to the Custom Fields page in your UI, disclosing the "DB Column" column using the column selector, and then looking for warning text.

Screen Shot 2022-06-27 at 2 00 32 PM

Output of the console log looks like this:

Screen Shot 2022-06-27 at 1 57 06 PM

LDAP Validation

Since LDAP configuration is clunky and difficult and is a common source of frustration for our users, this PR throws errors on the LDAP settings page if we detect any of the most common wrong settings. While this is not a panacea, it will at least hopefully provide some more useful feedback to the user so they can see what might be wrong.

Note: this happens on the LDAP settings page LOAD, not SAVE. We're not actually interfering with the user's data submission, but we're making it clear that it's unlikely to work. This does not modify the behavior of LDAP or the saved settings in any way.

Screen Shot 2022-06-30 at 3 15 30 PM

Email User a List of Items Checked Out

We've also introduced a new feature that allows you to send a user a copy of all of the assets, licenses, etc from the user's profile page.

View_User_Snipe_E__Head____Snipe-IT_Demo_Test

Personal API Token Console Command

We've added the ability to generate API tokens via a new console command: 

php artisan snipeit:make-api-key --help
php artisan snipeit:make-api-key --user_id=1 --key-only
php artisan snipeit:make-api-key --user_id=1
php artisan snipeit:make-api-key --user_id=1 > api.txt

Screen Shot 2022-06-28 at 10 27 26 PM

Potentially Confusing / Breaking Changes

Purging data and backup deletion must now be enabled in the .env file*

This is just an additional security measure put in place so that a bad actor within an organization can no longer delete backups or purge deleted data. It defaults to DISABLED, so if you don't see your backup delete icons or your purge isn't working, be sure to enable it using the new ALLOW_BACKUP_DELETE and ALLOW_DATA_PURGE environmental variables. (You'll have to add those to your .env if this is an upgrade.) We recommend keeping this disabled until you actually have to perform those tasks, and then disabling it once you're done. You can read more about that here.

Fixed a bug in Depreciation math

Back in February, we introduced a bug that made the calculation of depreciated values to be a little... well, wonky. We've reverted that change and Depreciation calculations should be working again.

New disclosure arrows on Asset Create/Edit and User Create/Edit

We think this is a cool feature, but it could be confusing at first. We now have disclosure arrows for the optional sections of user and asset creation, which should keep the screen less cluttered for people who don't use all of the optional fields. Once you expand the arrows, that state will be remembered via browser cookie.

Screen.Recording.2022-06-27.at.10.48.42.AM.mov

Updated Assets Counts

If you do NOT have the 'Show archived assets in the "all assets" listing' option checked in Admin Settings > General Settings, your dashboard count totals and totals on your tabbed interfaces will have changed to only include non-archived assets.

What's Changed in v6.0.6

New Contributors

Full Changelog: v6.0.5...v6.0.6

Check out latest releases or
releases around snipe/snipe-it v6.0.6

Don't miss a new snipe-it release

NewReleases is sending notifications on new releases.

Get notifications