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

Change Provider NOC/Admin Fields to GitHub-Flavored Markdown #2360

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

Originally created by @hSaria on GitHub (Feb 11, 2019).

Environment

  • Python version: 3.6.6
  • NetBox version: 2.5.5

Proposed Functionality

In circuits/providers/, change the NOC and Admin contact fields to be GitHub-Flavored Markdown fields (similar to the Comments field).

Use Case

The NOC and Admin fields may contain information related to more than one person/department. For instance, you may have different admin contacts for different roles. Markdown would help structure those two fields.

Database Changes

None.

External Dependencies

None.

Originally created by @hSaria on GitHub (Feb 11, 2019). ### Environment * Python version: 3.6.6 * NetBox version: 2.5.5 ### Proposed Functionality In `circuits/providers/`, change the NOC and Admin contact fields to be GitHub-Flavored Markdown fields (similar to the Comments field). ### Use Case The NOC and Admin fields may contain information related to more than one person/department. For instance, you may have different admin contacts for different roles. Markdown would help structure those two fields. ### Database Changes None. ### External Dependencies None.
adam added the status: acceptedtype: feature labels 2025-12-29 17:25:15 +01:00
adam closed this issue 2025-12-29 17:25:15 +01:00
adam commented 2025-12-29 17:25:16 +01:00
Author
Owner
Copy Link

@Bill-Irvine commented on GitHub (Feb 17, 2019):

I've got a similar feature request that has been accepted. Maybe this will fit your purpose?

https://github.com/digitalocean/netbox/issues/1344

@Bill-Irvine commented on GitHub (Feb 17, 2019): I've got a similar feature request that has been accepted. Maybe this will fit your purpose? https://github.com/digitalocean/netbox/issues/1344
adam commented 2025-12-29 17:25:16 +01:00
Author
Owner
Copy Link

@hSaria commented on GitHub (Feb 17, 2019):

It does fit the purpose, though I'm very sure it requires a bit more effort (new object type, likely to change database structure, etc...). For this request, I simply ask that those two fields are formatted similar to the comments section. This change, as far as I can tell, should be quite simple.

Long term, I'd prefer your approach as it is way more scalable, though it seems the devs are busy with other things, so I tried suggesting a middle-ground solution.

@hSaria commented on GitHub (Feb 17, 2019): It does fit the purpose, though I'm very sure it requires a bit more effort (new object type, likely to change database structure, etc...). For this request, I simply ask that those two fields are formatted similar to the comments section. This change, as far as I can tell, should be quite simple. Long term, I'd prefer your approach as it is way more scalable, though it seems the devs are busy with other things, so I tried suggesting a middle-ground solution.
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 status: accepted 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#2360
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?