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.

Sign up for GitHub

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

Jump to bottom

Incorrect redirection after editing a prefix in the Aggregate - Prefixes tab #8717

Closed
markkuleinio opened this issue Feb 22, 2022 · 0 comments
Closed

Incorrect redirection after editing a prefix in the Aggregate - Prefixes tab #8717

markkuleinio opened this issue Feb 22, 2022 · 0 comments
Assignees
@jeremystretch
Labels
status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application

Comments

@markkuleinio
Copy link
Contributor

NetBox version

v3.1.8

Python version

3.9

Steps to Reproduce

  1. Create a RIR "Test"
  2. Create aggregate 99.99.99.0/24 (RIR = Test)
  3. Go to Prefixes tab in the aggregate
  4. Click Add Prefix - 99.99.99.0/28 - Create
  5. Go to aggregate 99.99.99.0/24 - Prefixes tab
  6. Select (using checkbox) prefix 99.99.99.0/28 - Edit
  7. Enter description "Test" - Apply

Expected Behavior

The Prefixes tab of aggregate 99.99.99.0/24 is shown.

Observed Behavior

The URL /ipam/prefixes/xx/prefixes is shown (= some prefix with ID of xx is shown, or Page Not Found is received).

It should redirect to /ipam/aggregates/xx/prefixes instead.
@markkuleinio markkuleinio added the type: bug A confirmed report of unexpected behavior in the application label Feb 22, 2022
@jeremystretch jeremystretch added the status: accepted This issue has been accepted for implementation label Feb 22, 2022
@jeremystretch jeremystretch self-assigned this Feb 22, 2022
@jeremystretch jeremystretch mentioned this issue Mar 7, 2022
Merged
@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 24, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@jeremystretch jeremystretch

Labels
status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jeremystretch @markkuleinio