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

Rich Text Copy-Paste Issue for Status Field #10002

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

Originally created by @opericgithub on GitHub (Jul 23, 2024).

NetBox version

v4.0.7

Feature type

Change to existing functionality

Proposed functionality

Our employees need to export data from NetBox to Outlook emails using copy-paste in html or rich text format. In NetBox version 3.x, when data is pasted into Outlook, the background of the status field is displayed correctly (e.g., the background is green, and the text is white). However, in version 4.x, the background is white along with the text, making the status field's value indistinguishable.

Attached are screenshots from NetBox versions 3.x and 4.x illustrating the difference in the display of the status field background when copying and pasting into Outlook:

Screenshot from NetBox version 3.x:

image

Screenshot from NetBox version 4.x:

image

In the fourth row, I intentionally changed the background color in Outlook to illustrate the issue I am reporting.

Use case

This functionality is crucial for our operations as it allows for efficient and clear data sharing among employees.

Database changes

No response

External dependencies

No response

Originally created by @opericgithub on GitHub (Jul 23, 2024). ### NetBox version v4.0.7 ### Feature type Change to existing functionality ### Proposed functionality Our employees need to export data from NetBox to Outlook emails using copy-paste in html or rich text format. In NetBox version 3.x, when data is pasted into Outlook, the background of the status field is displayed correctly (e.g., the background is green, and the text is white). However, in version 4.x, the background is white along with the text, making the status field's value indistinguishable. Attached are screenshots from NetBox versions 3.x and 4.x illustrating the difference in the display of the status field background when copying and pasting into Outlook: Screenshot from NetBox version 3.x: ![image](https://github.com/user-attachments/assets/3848ee8a-41f0-4a23-8b05-1efad4b0a42b) Screenshot from NetBox version 4.x: ![image](https://github.com/user-attachments/assets/1e10032e-997c-424d-ad41-4a605ae4d135) In the fourth row, I intentionally changed the background color in Outlook to illustrate the issue I am reporting. ### Use case This functionality is crucial for our operations as it allows for efficient and clear data sharing among employees. ### Database changes _No response_ ### External dependencies _No response_
adam added the type: featurepending closurestatus: under reviewnetboxtopic: UI/UX labels 2025-12-29 21:25:29 +01:00
adam closed this issue 2025-12-29 21:25:29 +01:00
adam commented 2025-12-29 21:25:30 +01:00
Author
Owner
Copy Link

@jeffgdotorg commented on GitHub (Jul 24, 2024):

Thanks for catching this need.

I've moved this issue to needs owner status. If you're interested in working it through to a PR, please leave a comment to that effect and a maintainer will assign it to you for implementation. Otherwise, another developer with the necessary skills and capacity can pick it up.

I'm setting your issue's milestone to v4.1 because a significant rework of the UI is coming in that release, whose first beta is due in early August. If somebody picks up this issue before then, and it turns out to be easy to cherry-pick the work to a v4.0 patch release, we should also do that.

@jeffgdotorg commented on GitHub (Jul 24, 2024): Thanks for catching this need. I've moved this issue to `needs owner` status. If you're interested in working it through to a PR, please leave a comment to that effect and a maintainer will assign it to you for implementation. Otherwise, another developer with the necessary skills and capacity can pick it up. I'm setting your issue's milestone to `v4.1` because a significant rework of the UI is coming in that release, whose first beta is due in early August. If somebody picks up this issue before then, and it turns out to be easy to cherry-pick the work to a v4.0 patch release, we should also do that.
adam commented 2025-12-29 21:25:30 +01:00
Author
Owner
Copy Link

@opericgithub commented on GitHub (Sep 4, 2024):

Thank you for the attention given to this issue and for moving it under review. I really appreciate the efforts so far.
As it's been a little while since the last update, I wanted to kindly check in and see if there has been any progress or if there are any additional details you might need from me to help move this forward.

@opericgithub commented on GitHub (Sep 4, 2024): Thank you for the attention given to this issue and for moving it under review. I really appreciate the efforts so far. As it's been a little while since the last update, I wanted to kindly check in and see if there has been any progress or if there are any additional details you might need from me to help move this forward.
adam commented 2025-12-29 21:25:30 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Apr 25, 2025):

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 (Apr 25, 2025): 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/main/CONTRIBUTING.md).
adam commented 2025-12-29 21:25:30 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (May 25, 2025):

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 (May 25, 2025): 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 netbox pending closure status: under review topic: UI/UX 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#10002
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?