Existing instrument picker answers can cause errors

UserOfficeProject / issue-tracker

Shared place for features and bugs from all collaborators.

0 stars 0 forks source link

Closed simonfernandes closed 1 month ago

simonfernandes commented 2 months ago

There are a couple of issues with the answers to instrument picker questions:

Some instrument picker answers have not been caught by the backwards compatibility script. This results in N/A being shown when viewing the answer.
Setting the time requested to NULL causes an error when saving or proceeding to the next step, when cloning a proposal to a call that doesn't require a time allocation (e.g. Rapid).

simonfernandes commented 1 month ago

The temporary workaround is to either

Change the answer in the database so that the timeRequested is "0" instead of null
Change the instrument in the frontend, proceed, then change it back and proceed