[feature] Create A Copy with Immediate Edit

[jolpadgett]

Version and OS
0.47.06 docker

Is your feature request related to a problem? Please describe.
When adding multiple watches where the watched url is the only change, Create A Copy button creates an exact active copy and goes back to the list of watches from which I must quickly click edit and make my changes. This process also carries forward the history so there is always a change notification after saving the updated watch.

Describe the solution you'd like
An option for current Create A Copy or a new button where the copy is created and the user is immediately pushed to the edit page for the copied watch. The history of the copied watch is cleared. No new watch is created, however, until the Save button is pressed on the edit screen. Bonus: if the “Extract <title> from document and use as watch title” is checked, clear the title of the copied watch so it can be populated on first check of the new watch. Effectively using an existing watch as a template or prototype for a new but distinct watch.

Describe the use-case and give concrete real-world examples
Using to monitor new books for authors on GoodReads, with the best settings configured on an existing watch. Adding a new author’s books watch, I would edit existing watch, click Create A Copy And Edit and then update the url to point to the to-be-added author’s book list page and save the watch. Since the prototype’s watch history and title is cleared, the newly created watch functions as a brand new watch so there isn’t a massive change notification detailing the prototype’s author’s book list versus the new author’s book list and the title is updated with the watched URL’s webpage title instead of retaining the prototype’s existing title.

Additional context
Add any other context or screenshots about the feature request here.

[dgtlmoon]

hmm yeah like "Save and clone"

or maybe the "save" button can have some dropdown like

so you can select "Save" or "save , clone/edit"

[dgtlmoon]

actually wondering if "clone" needs to keep the history at all

[jolpadgett]

With this approach, I say “no history”. Since we would be creating a new and distinct watch, its state (including history) should be the same as a new from scratch watch.