Feature Request: Checkout to Department

[Krejar]

Server (please complete the following information):

• v4.9.4
• Centos 8
• Apache
• 7.4

Describe the solution you'd like
I would like to see an option to Checkout to Department

Describe alternatives you've considered
I thought about creating a "People" entry for location, but then decided against that. I've been using Location as a placeholder for Department, but I am now 20+ entries for Location when in reality I only have 5-7 different locations.

Additional context
This isn't a huge deal breaker for me, more of a QoL. I would love to see it implemented as I have many assets that are checked out department wide and moved around quite a bit between locations.

[snipe]

That's unlikely to be on our short term roadmap. We already allow you to checkout to location, which is problematic enough, since a Location cannot be held responsible for lost/stolen/damaged goods.

[Krejar]

Hi @snipe

Thank you for the very quick reply.

Why was Location included in the Checkout to selection if it couldn't be responsible for equipment? This makes absolute sense as a Location is a place and not a person or persons. However a department is a person or a group of people. I suppose I could assign the asset to a department head, but if that person changes positions or is terminated, then I would need to assign the asset to another person. To include a Department as a Checkout to selection would satisfy the use case of an entity not being held responsible for lost goods, etc.

[stale]

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 has been automatically closed because it has not had recent activity. If you believe this is still an issue, please confirm that this issue is still happening in the most recent version of Snipe-IT and reply to this thread to re-open it.