Option to keep roast notes after Reset

[lookingafar]

Is your feature request related to a problem? Please describe.
My machine allows only 5 second sampling interval, so I have to leave notes about every roasts: exact development time, exact drop temperature, sometimes previous roast drop temperature and development time. I use these notes during roasting to check the exact development time and, sometimes, exact drop temperature. Before using Artisan plus I just left the notes in the bean text field, since they are not deleted on reset, open the last roast, check the notes, reset the roast (the notes would still be there), roast the next batch. If Artisan is connected to Artisan plus, however, those notes get replaced by bean data, which is fine. However, on "Notes" tab roasting notes get deleted on Reset as well. So, maybe there should be an option not to delete roast notes on Reset?

Describe the solution you'd like
An option, similar to "Delete roast properties on Reset" that allows to keep roast notes after Reset.

Describe alternatives you've considered
Copy and paste, which is not very convenient. Or not to use Artisan Plus.

[DennieSch]

Greetings,
Just thought I would throw in my support for something like is suggested above.
I roast smaller batches (Behmor) and at times, do back-to-back roasts (and sometimes x3) of the same beans to achieve a larger roast quantity. While I don't do Cupping myself, I do add the cupping notes provided by the bean supplier into Cupping Notes. Having the ability to selectively not reset these entries could be very helpful when doing 'back-to-backs'.

Maybe something like the following could work for folks in these situations. Just a suggestion.
Cheers,
Dennie

Delete properties on Reset

• Roast
• Roasting Notes
• Cupping Notes
• Cup Profile

[scottjames]

What is the best place to add this? I'm thinking to include this in restoreExtraDeviceSettingsBackup() with the other things that get set after a reset() call.

restoreExtraDeviceSettingsBackup

Could these settings be preserved in the extra device settings backup area, then restored in this function?

[MAKOMO]

We won't add any further configuration on this as this would just add to the confusion. There are conflicting workflows here (see discussion of Issue #1521). I don't see a good way to make all happy.

NOTE: the restoreExtraDeviceSettingsBackup() mechanism has a completely different purpose. This is not an implementation problem, but a design issue.

[DennieSch]

I can understand. There are probably many different workflows out there and it would be difficult (and confusing) to try and satisfy all of them.

I roast with a Behmor and do back-to-backs of the same beans and amounts at times. For example, this past weekend I did 4 roasts of the same beans and amount.
What I did was -

• ran the first roast
• saved that roast
• did a Reset without clearing properties
• clicked 'ON'
• opened the first roast which comes up in the 'Reader' instance of Artisan
• did a copy and paste from the 'Reader' instance of the first roast (e.g. Roast Notes, Cup Notes) into the 2nd, 3rd and 4th when they were run.
• This works for me so I'm...good-to-go!

While having the selective clearing of properties would be nice, I've got a process that works fine for me.

Cheers,
Dennie