starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-11 21:10:29 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Order items inside a widget in the dashboard #7888

New Issue
Closed
opened 2025-12-29 20:29:35 +01:00 by adam · 4 comments
adam commented 2025-12-29 20:29:35 +01:00
Owner
Copy Link

Originally created by @mmfreitas on GitHub (Apr 11, 2023).

NetBox version

v3.5.0-dev

Feature type

New functionality

Proposed functionality

We would like to be able to order items inside a card widget on the new dashboard.

Could this be accomplished by using the same way that columns are organized in tables? Through the "configure table" button and use that same logic to reorder inside the widget.

Instead of having this field type inside the widget definition:
image

Have this:
image

Instead of columns the objects on the list would be the models. This should also allow for multiple selection and quick organization in removing or adding items in certain widget.

Another way could be to drag and drop inside the widget (only needs to move up or down), the same way the widgets are draggable.
Not sure which is easier to implement at this stage or if any of these proposals are feasible...

Use case

This would allow for more customization, instead of having it alphabetically ordered.

Database changes

Not sure if any are required.

External dependencies

No response

Originally created by @mmfreitas on GitHub (Apr 11, 2023). ### NetBox version v3.5.0-dev ### Feature type New functionality ### Proposed functionality We would like to be able to order items inside a card widget on the new dashboard. Could this be accomplished by using the same way that columns are organized in tables? Through the "configure table" button and use that same logic to reorder inside the widget. Instead of having this field type inside the widget definition: ![image](https://user-images.githubusercontent.com/91552302/231214668-bdaa4feb-ec90-471b-a899-4babd2b07656.png) Have this: ![image](https://user-images.githubusercontent.com/91552302/231212058-97d5efeb-9cd6-4803-9682-5f73c92876bc.png) Instead of columns the objects on the list would be the models. This should also allow for multiple selection and quick organization in removing or adding items in certain widget. Another way could be to drag and drop inside the widget (only needs to move up or down), the same way the widgets are draggable. Not sure which is easier to implement at this stage or if any of these proposals are feasible... ### Use case This would allow for more customization, instead of having it alphabetically ordered. ### Database changes Not sure if any are required. ### External dependencies _No response_
adam added the type: featurestatus: needs ownerpending closure labels 2025-12-29 20:29:35 +01:00
adam closed this issue 2025-12-29 20:29:35 +01:00
adam commented 2025-12-29 20:29:36 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Apr 11, 2023):

We would like to be able to order items inside a card widget on the new dashboard.

How? Please edit your post above to include more detail about the proposed change(s).

@jeremystretch commented on GitHub (Apr 11, 2023): > We would like to be able to order items inside a card widget on the new dashboard. How? Please edit your post above to include more detail about the proposed change(s).
adam commented 2025-12-29 20:29:36 +01:00
Author
Owner
Copy Link

@mmfreitas commented on GitHub (Apr 11, 2023):

How? Please edit your post above to include more detail about the proposed change(s).

I've edited the above post to try and better explain myself.

@mmfreitas commented on GitHub (Apr 11, 2023): > How? Please edit your post above to include more detail about the proposed change(s). I've edited the above post to try and better explain myself.
adam commented 2025-12-29 20:29:36 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Aug 3, 2023):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Do not attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our contributing guide.

@github-actions[bot] commented on GitHub (Aug 3, 2023): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. **Do not** attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).
adam commented 2025-12-29 20:29:37 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Sep 3, 2023):

This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.

@github-actions[bot] commented on GitHub (Sep 3, 2023): This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
beta
breaking change
complexity: high
complexity: low
complexity: medium
needs milestone
netbox
pending closure
plugin candidate
pull-request
Mirrored from GitHub Pull Request
 severity: high
severity: low
severity: medium
status: accepted
status: backlog
status: blocked
status: duplicate
status: needs owner
status: needs triage
status: revisions needed
status: under review
topic: GraphQL
topic: Internationalization
topic: OpenAPI
topic: UI/UX
topic: cabling
topic: event rules
topic: htmx navigation
topic: industrialization
topic: migrations
topic: plugins
topic: scripts
topic: templating
topic: testing
type: bug
type: deprecation
type: documentation
type: feature
type: housekeeping
type: translation
No Label pending closure status: needs owner type: feature
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#7888
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?