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

Clone a computed field and carry over select fields #698

Closed
FragmentedPacket opened this issue Jul 14, 2021 · 2 comments · Fixed by #704
Closed

Clone a computed field and carry over select fields #698

FragmentedPacket opened this issue Jul 14, 2021 · 2 comments · Fixed by #704
Assignees

Comments

@FragmentedPacket
Copy link
Contributor

Environment

  • Python version: 3.6
  • Nautobot version: 1.1.0b2

Proposed Functionality

When I click Clone on an existing Computed Field, I'd like for some of the fields to be carried over to the new form.

Use Case

Don't want to have to repopulate all fields again when cloning a computed field.
image

Now if I click Clone. It brings up the new form, but it's blank.
image

I would say we should probably carry over the following:

  • Content Type
  • Description
  • Template
  • Fallback Value
  • Weight

I don't feel passionate about all the fields, but do what y'all think is best.

Database Changes

None

External Dependencies

None

@FragmentedPacket
Copy link
Contributor Author

I can implement whichever way y'all want to go with this. Let me know.

@glennmatthews
Copy link
Contributor

Thank you! Your proposed list of carry-over attributes looks good to me. Go for it!

jathanism added a commit that referenced this issue Jul 19, 2021
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Oct 18, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants