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

"Add export template" button doesn't pass content type #15084

Closed
alehaa opened this issue Feb 8, 2024 · 1 comment
Closed

"Add export template" button doesn't pass content type #15084

alehaa opened this issue Feb 8, 2024 · 1 comment
Assignees
Labels
severity: low Does not significantly disrupt application functionality, or a workaround is available status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application

Comments

@alehaa
Copy link
Contributor

alehaa commented Feb 8, 2024

Deployment Type

Self-hosted

NetBox Version

v3.7.2

Python Version

3.11

Steps to Reproduce

  1. Navigate to Customization > Export Templates.
  2. Click button Export > Add export template...

Expected Behavior

Form has field Content types prefilled.

Observed Behavior

Field Content types is empty, as URL parameter is not properly set. It needs to be content_types not content_type (missing s).

I can provide a PR for this issue.

@alehaa alehaa added the type: bug A confirmed report of unexpected behavior in the application label Feb 8, 2024
@jeremystretch jeremystretch self-assigned this Feb 8, 2024
@jeremystretch jeremystretch added status: accepted This issue has been accepted for implementation severity: low Does not significantly disrupt application functionality, or a workaround is available labels Feb 8, 2024
@jeremystretch
Copy link
Member

  1. Navigate to Customization > Export Templates.

Just to clarify because this could be confusing: The bug affects the "add export template" dropdown item under the "export" button for all objects.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 9, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
severity: low Does not significantly disrupt application functionality, or a workaround is available status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application
Projects
None yet
Development

No branches or pull requests

2 participants