At present, if the “Save log as target profile” button is not checked in the New Batch window prior to sending to the database, the existing workflows for setting that as a plan to use when roasting future batches are all awkward.
Option 1: Find the batch in the batch log, save the data to a file, import the file as a roasting plan.
Option 2: Log into the database in psql and create the appropriate record manually.
It would be better if the batch details window provided an option to set the roasting plan directly or if this was available in an interface for reviewing all potentially appropriate batches.
Streamlining this also makes it easier to defer the decision regarding if that data should be set as the roasting plan. For example, one might want to roast a few different variations and decide which to keep after taste testing.
At present, if the "Save log as target profile" button is not checked in the New Batch window prior to sending to the database, the existing workflows for setting that as a plan to use when roasting future batches are all awkward.
Option 1: Find the batch in the batch log, save the data to a file, import the file as a roasting plan.
Option 2: Log into the database in psql and create the appropriate record manually.
It would be better if the batch details window provided an option to set the roasting plan directly or if this was available in an interface for reviewing all potentially appropriate batches.
Streamlining this also makes it easier to defer the decision regarding if that data should be set as the roasting plan. For example, one might want to roast a few different variations and decide which to keep after taste testing.
At present, if the “Save log as target profile” button is not checked in the New Batch window prior to sending to the database, the existing workflows for setting that as a plan to use when roasting future batches are all awkward.
Option 1: Find the batch in the batch log, save the data to a file, import the file as a roasting plan. Option 2: Log into the database in psql and create the appropriate record manually.
It would be better if the batch details window provided an option to set the roasting plan directly or if this was available in an interface for reviewing all potentially appropriate batches.
Streamlining this also makes it easier to defer the decision regarding if that data should be set as the roasting plan. For example, one might want to roast a few different variations and decide which to keep after taste testing.