snipe / snipe-it Goto Github PK

They will have to be registered and logged in, but they can then reserve assets like set devices, etc.

Did you help close this issue? Go claim the $15 bounty on Bountysource.

View is looking for license info, but we're passing a seat ID now

Nice to have, not critical for MVP.

New field added to the asset log

With a small number of assets it may not be necessary as the assets/models are interactively shown as you type. However, it may be useful for larger data sets.

Add a field for postal/zip codes

It seemed like a good idea to have them separate before, but now I'm just not so sure. I think maybe adding a boolean 'license' field in the assets table to signify that it's not a piece of physical equipment might be better.

Let somebody else handle password hashing and storage.

Might not be feasible with Sentry, I'm not familiar enough with it to know how flexible it is. Rudimentary research shows others have forked it to add support for LDAP with mixed results.

phpipam uses adLDAP with great success (was the easiest AD integration I have ever experienced with a php app).

Awesome work so far! Let me dig in a little deeper and I hope to contribute and not just gripe about complicated stuff!

This might be another option.

It's mad janky, yo.

Not sure how it fell off.

See attached

in /app/models/Asset.php - it is made of fail right now. It mostly sorta works, but it's janky as hell.

chown -R 755 app/storage ; incorrect

its to be corrected to

chmod -R 755 app/storage

Currently it's unsorted, make the columns sortable.

This only counts assets now, not licenses, since I changed the way licenses work

Some sort of status field for when assets are not deployed or deployable. I'm thinking a status field. When something gets marked as out for maintenance, etc, it gets automatically un-assigned from the user it was assigned to.

Right now, depreciation shows up in an asset edit form, but isn't actually saved anywhere. It's saved in the Asset Model view, but not on the individual asset level. If I'm going to leave it only at the model level, I should remove it from the asset form to avoid confusion, as it's just BAS right now. (Broke As Shit.)

Depreciations isn't seeded to start with (which should be fixed) but it shouldn't blow up even if there are none.

Definitely not a priority, but some people think in terms of dates better when looking at a calendar-ish view.

Did you help close this issue? Go claim the $20 bounty on Bountysource.

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

Fields are hidden but you can't scroll over to them.

I found 3 area with XSS.

1. Create an Model with a name of <script>alert('a')</script>
   1a. Click Delete the alert pops up twice
   1b. Add an asset and click on the models drop down the alert shows up
2. Create an Asset with a name of <script>alert(1)</script>
   2a. Click Delete, the alert shows up twice

To keep a running record of maintenance on machines, etc

Did you help close this issue? Go claim the $100 bounty on Bountysource.

Will need to check that assigned users aren't orphaned, that the existing checked out users don't get overwritten, etc.

Location of the asset matters for tax purposes, so a location needs to be associated with each user/asset.

Right now, the dashboard just points to the assets index. Would like a nice overview of assets, things coming due, etc.

Previously would check the assigned_to field, but that field no longer exists because of the new license join table

Right now, you can create orphaned assets, etc. Need to error check that and prevent that from happening.

A few different ways I could handle this here, need to spend some time thinking about the best way.

A user wouldn't request a specific laptop that was already checked out to a standard user as their normal laptop, but they may want to request a test device, etc. Should probability have some way of marking which ones can be reserved.

This is a fringe case, but it just so happens to apply in my case. My IT team services two sister companies within a parent holding company. Adding this as an enhancement, but unless I hear from other folks who really want this, it's low priority for now.

The $500 bounty on this issue has been claimed at Bountysource.