snipe

You don't actually have to set either of those things. They're both optional. We can consider adding this, but it seems like a better way to handle it might be...

Use custom fields. That’s what they’re there for.

There are already two. RTD (ready to deploy) location and actual location. I’m not sure a third would be a great idea.

I'm still kind of unclear on the use case here. We provide two location fields, Default Location (where the asset is when it's unassigned) and Location (which can be assumed...

That makes sense, I'm just honestly not sure how to have it without it very potentially screwing up data later on, since we *do* that inheritance process for assets. The...

Yeah, it's more the location inheritance that we have to worry about I think. If the expected behavior is that the location is inherited from whoever it's checked out to,...

@bzeus - can you confirm this bug for me please? Danke!

It's not really an issue, it's a feature request, and we haven't added that functionality yet. Kits are brand new and we'll be adding to their functionality over time.

100% - it was the original goal that accessories would be included, but there was a fatal bug in the way it was executed that we had to pull some...

Folks - please write these in English. My french is *awful*, and I'd like to understand what the ask is here.