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

Allow associating an export template with multiple object types #10761

Closed
jeremystretch opened this issue Oct 26, 2022 · 0 comments
Closed

Allow associating an export template with multiple object types #10761

jeremystretch opened this issue Oct 26, 2022 · 0 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

NetBox version

v3.3.6

Feature type

Change to existing functionality

Proposed functionality

Change the content_type field on the ExportTemplate to a many-to-many relationship to ContentType, to enable associating an export template to multiple types. (This is essentially replicating #8274 for export templates instead of custom links.)

Use case

This change would allow the reuse of export templates across multiple object types.

Database changes

No response

External dependencies

No response

@jeremystretch jeremystretch added status: accepted This issue has been accepted for implementation type: feature Introduction of new functionality to the application labels Oct 26, 2022
@jeremystretch jeremystretch added this to the v3.4 milestone Oct 26, 2022
@jeremystretch jeremystretch self-assigned this Oct 26, 2022
jeremystretch added a commit that referenced this issue Oct 26, 2022
…content-types

Closes #10761: Enable associating an export template with multiple objects
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jan 25, 2023
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

1 participant