Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Include inventory items on primary device view #4956

Closed
jeremystretch opened this issue Aug 5, 2020 · 5 comments
Closed

Include inventory items on primary device view #4956

jeremystretch opened this issue Aug 5, 2020 · 5 comments
Assignees
Labels
status: accepted This issue has been accepted for implementation type: feature Introduction of new functionality to the application
Milestone

Comments

@jeremystretch
Copy link
Member

jeremystretch commented Aug 5, 2020

Environment

  • Python version: 3.6.9
  • NetBox version: 2.9-beta1

Proposed Functionality

Show inventory items on the primary device view, in a table similar to how other components are now displayed.

inventory_tab

Use Case

There is no real need for a separate view, and merging it into the primary device view avoids minor bugs like #4951.

Database Changes

None

External Dependencies

None

@jeremystretch jeremystretch added type: feature Introduction of new functionality to the application status: under review Further discussion is needed to determine this issue's scope and/or implementation beta Concerns a bug/feature in a beta release labels Aug 5, 2020
@jeremystretch
Copy link
Member Author

I recall now why we've kept it as a separate view: the parent field on InventoryItem is a regular ForeignKey, not an MPTT field, so constructing the hierarchy of nested items is rather inefficient. #1846 was opened a long time ago for this work, but it has yet to be implemented. Now might actually be a good time to take it on, though I haven't yet dug into how involved the migration will be.

@a31amit
Copy link

a31amit commented Aug 5, 2020

While merging into the primary device view can be good to avoid such minor bugs. But I personally vote to keep inventory items tab separately where my thoughts are aligned with ease of use/view inventory items. Especially when you have a few custom links added.

with this, when I currently view the inventory tab and wanted to open custom links, these are mostly on the same screen. As part of user experience, it's very easy to open those links, especially when the decision to open links depends on what data is in inventory. Such as links to purchase requests app /other applications.

With proposed functionality, inventory items go very below to Device page, where you can't which server you are adding items can lead to mis-update information if working on multiple pages. Also to view any links, users have to go all the way to top or scroll back to open those links.

Other than this, the inventory items tab currently can be more customized if the user wanted to display any other information, which either not included with core netbox or maybe instance/needs depends, if this is moved, users might not have the choice to that.

@jeremystretch jeremystretch added status: blocked Another issue or external requirement is preventing implementation and removed beta Concerns a bug/feature in a beta release status: under review Further discussion is needed to determine this issue's scope and/or implementation labels Aug 6, 2020
@jeremystretch
Copy link
Member Author

Blocked by #1846

@jeremystretch jeremystretch added status: accepted This issue has been accepted for implementation and removed status: blocked Another issue or external requirement is preventing implementation labels Sep 18, 2020
@jeremystretch jeremystretch added this to the v2.10 milestone Sep 18, 2020
@jeremystretch
Copy link
Member Author

@a31amit if your concern is primarily just being able to view custom links and the object table at the same time, we can move the device details into a separate sub-tab alongside the components. This would address the UX issue for all components, not just inventory items.

Screenshot_2020-09-18 MyDevice1 - NetBox

@a31amit
Copy link

a31amit commented Sep 19, 2020

@jeremystretch Thanks, This resolves my concerns. Since it doesn't seem to include any breaking changes, would be happy to see this in the next release of netbox rather wait for the 2.10 version.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Dec 19, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
status: accepted This issue has been accepted for implementation type: feature Introduction of new functionality to the application
Projects
None yet
Development

No branches or pull requests

2 participants