github grokability/snipe-it v8.3.6

8 hours ago

Caution

For some reason, Github's built-in redirect from snipe/snipe-it to grokability/snipe-it has stopped working. If you're trying to upgrade or pull and you get a "not found" response or a login prompt from Github, do the following to set your origin to the correct Github URL:

git remote remove origin
git remote add origin https://github.com/grokability/snipe-it

Happy Monday! Snipe-IT v8.3.6 is out! We've made some improvements to the Unaccepted Items report, added file uploads to suppliers, and also added color tags to Locations, Companies, Departments, Suppliers, Categories, and Manufacturers. (Check out the docs here.) The new tag_color field is also available via the API for the affected object types.

e508c028a290c33e58cd03b87b8d52eeef7d0d2987443b8d2b17c63a24b5821b-frame_generic_light-15

We're also now sending an additional email header (X-System-Sender: Snipe-IT) for all notifications. This wouldn't affect anything related to notifications other than it allows clever folks to potentially apply filters on emails going to their inbox that have that header.

Additionally, if you have quite a lot of users and were unable to get the groups page to load in between v8.3.5 and v.8.3.6, that issue should be fixed. (It's a long, boring story related to default settings for max_input_vars and max_multipart_body_parts.) If you're still having problems, set your MAX_UNPAGINATED in your .env to something under 5000.

We know this isn't ideal, since being able to add users to from the groups page was a great new feature, but for users with very large user sets, this was a bit of a dealbreaker. Don't worry - we're working on figuring out a way that makes sense from a UX perspective. (For example, "select all users" when the user list is paginated would take a very long time, since you'd have to select them all individually.)

API changes

  • Added tag_color to Locations, Companies, Departments, Suppliers, Categories, and Manufacturers
  • If you were incorrectly passing the filter parameter to the Assets or Users endpoints (for example, /api/v1/users?filter=email:you@example.org), it would previously 500. It now returns a validation error, as that endpoint is looking for JSON (for example /api/v1/users?filter={"email":"you@example.org"}.)

What's Changed

New Contributors

Full Changelog: v8.3.5...v8.3.6

Don't miss a new snipe-it release

NewReleases is sending notifications on new releases.