Open MSWork79 opened 6 years ago
Yes, This issue or feature request is still important. Please re-open it for now.
Okay, it looks like this issue or feature request might still be important. We'll re-open it for now. Thank you for letting us know!
+1, would really find this useful in EDU.
And another +1
And +1 here as well. Would be handy for generating recursive asset reports by parent categories. I think limiting it to 3-4 levels deep would be a good place to start if going beyond that renders problems.
Thanks!
+1 here as well!
+1. Restrict recursion to a sensible level, by all means. But this is required to get value from the parent/child function.
this would be helpful for sure
+1
absolutely love this feature request.
Our structure is thankfully fairly 'basic':
Company (Not a location) Parent Location: Office 1 - Office 2 - Office 3 - Office 4 - Office 5 Child Locations: Room 1, Room 2.. Room 1, Room 2.. Room 1, Room 2.. Room 1, Room 2.. Room 1, Room 2..
Much like the initial post here and the image in the comments we thought the assets would appear aggregated in totals etc. The other part which was quite surprising was that users in the users lists for the "Office" location did not appear there either. We have assigned staff to the Child locations (offices/desks). Would find it extremely useful to have the Rooms asset totals aggregate up to the Office totals visually on screen.
I promise I am not trying to make this more complicated but the other thing I was surprised not to see was the other sub-locations not being listed under the parent location. Even if it is just a list (aka not itemizing assets)
+1
+1 FD
Just bumping this since I'm here to ward off stale bots.
+1 on our end. I was training an admin to start auditing our assets by way of the reporting function. The inability of parent item to see child items removes the admin's ability to print a single report and walk around with it. They'd need to print 250 reports, one for each area in the office. .....
Perhaps in our specific case that could be remedied by a report generation modification? Ie: A checkbox reading "Generate reports for all child items".
+1
Will ever be an option to create a report in parent-child correlation? It makes no sense to create child locations without it. Thanks!
+1, at the very least for reporting
If everybody who commented +1 would vote with a 👍 at the top instead, this would be the 3rd most requested feature (~30 votes). This might be more helpful for the devs when planning their roadmap. Also notice that it's marked "Ready for dev", so think about contributing.
+1
Hi,
Please fix this, because it will help us a lot in our daily tasks.
Thanks!
+1 as it would be a perfect addition when looking at large storage locations with multiple areas
+1 It will be useful for my case.
My case: handling with many electronics components and other stuff in separate locations. I want to see all items in all child locations. In particular, in electronic component storage I want to see what is in some cell.
+1 Yes please
+1 this feature would be a game changer for us
Only way I can see this working is de-normalizing. Otherwise the joins will kill performance.
Only way I can see this working is de-normalizing. Otherwise the joins will kill performance.
I'm not a programmer.. but even I know what I'm about to suggest is sloppy. At minimum could the reports page facilitate a "child item report" queue and at least create them all individually? Depending on the data type they could be merged later by handy users. Would band-aid the problem in my opinion but may be better than nothing.
@stephenregisterTJT well, it's not just children, it's grandchildren, and great-grandchildren - which is why we have to de-norm. Those recursive queries are easy peasy when you have 10 locations and 1000 assets but get VERY expensive (speed/efficiency-wise) on larger data sets. So to implement this as you're suggesting would create inaccurate data, which is worse than no data :(
@stephenregisterTJT well, it's not just children, it's grandchildren, and great-grandchildren - which is why we have to de-norm. Those recursive queries are easy peasy when you have 10 locations and 1000 assets. So to implement this as you're suggesting would create inaccurate data, which is worse than no data :(
Aye, and this is why you're the expert. Thanks for the explanation. I'll keep holding out hope!
We've de-normed for performance before (last_checkout
, checkout_requests
, etc on the assets
table are 100% de-normalized so we don't have to ask the question of the action_logs
table, which can easily be millions of rows of data). So it's not out of the question at all, we just need to de-norm it in a way that is as close to unflappable as possible.
Modified Preorder Tree Traversal (MPTT) I believe suites parent/child for Locations well.
+1 I'd expected this behavior - I'd expected an asset record request for a Parent Location to include Child Locations. I just have one level (children). It's problematic that this feature isn't available. Will need to adjust strategy. Thank you for the program!
+1 When requesting an asset over the API, could the respones include a citation to the parent location?
Modified Preorder Tree Traversal (MPTT) I believe suites parent/child for Locations well.
MPTT Laravel package seems to be actively maintained. https://github.com/lazychaser/laravel-nestedset
GitHubEffective tree structures in Laravel 4-8. Contribute to lazychaser/laravel-nestedset development by creating an account on GitHub.
Did anyone come up with a solution for this one
When you get this working, could you also make the child locations nest under the parent locations on the locations page? Right now, it looks pretty jumbled. Sorting on parent helps somewhat but it still takes a moment to first look at the parent then locate the parent in the location name column and work your way up the chain to top level location.
+1 for this feature!
+1 for me. I've been looking forward to this feature. We have a lot of equipment assigned directly to classrooms. So our parent/child hierarchy would be like this:
Parent location: Bay City (we have multiple building within this city) Bay City child location: Education Center Education Center child location: Classroom 505 Education Center child location: Classroom 510
We have an area manager that oversees several parent locations. We would like to set them as the location manager within Snipe-IT, have them log in, and see all locations they manage and all assets within those locations using the parent/child hierarchy (all the way down to the classrooms).
+1 for this feature!
+1
Love to see this feature in the next release! :-)
+1 for this feature!
+1 for this feature!
+1
So far this is the only issue my team has found switching over to Snipe-IT. Thank you for all the hard work put into this project!
Loving this so far Being I set it up for a school child locations would be a great addition as we have multiple buildings in the district :) As of now I'm just suffixing all my locations with the Building-room-Number
+1 I would really like to have this feature to enable easier asset tracking (need to use at a university with buildings with multiple network closets in each closet).
+1
+1 This would be an extremely useful feature.
+1
+1 Would be really useful when trying to do auditing. Can check all the assets for a single department at once.
Expected Behavior (or desired behavior if a feature request)
CHS - Parent CHS Business Lab - Child
CHS - 2 assets CHS Business Lab - 25 assets
Expected Location CHS to have a total of 27 assets reported. (Parent + Child = Total)
Actual Behavior
CHS has 2 assets and does not factor in child quantities.
Please confirm you have done the following before posting your bug report:
Provide answers to these questions:
I have 25 assets assigned to a child location, and presently, the parent location does not reflect the quantity of assets in the child location.
Tried to reproduce, but there weren't any child locations and while I made one, I couldn't make a user move to it so I could manipulate the assets/locations/etc.
app/storage/logs
and your webserver's logs.\ n/a