You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
(How likely the bug is to happen, scored from 1-5. For example, probability of 5 is something like "it happens to all users every time they log in." whereas probability of 1 "only happens to certain users when a really specific and unlikely path is followed.")
Impact:
(How bad the bug is when it does happen, scored from 1-5. For example, effect of 5 is "the entire app crashes and makes it unusable for all users" or "the bug causes the wrong data to be saved, with critical information (e.g. payment) being affected." whereas effect of 1 is "It makes some styling look a little bit weird.")
Just adding that this bug doesn't appear to occur if you go in and add multiple operators after an Operation is already registered (i.e. edit the operation form). Or at least, it didn't happen in Dev when I tried it.
Blocked by: #2919 (there's a form refactor that partially fixes this)
Describe the Bug:
After adding multiple operators during registration, if you navigate back to the first page, the multiple operators are gone:
https://www.loom.com/share/54bf53ef344945ae9003ccbbb3def6be?sid=070186d3-1ba2-4c20-bcf4-b2ff2d4fe2b5
They're also not visible in administration:
They do appear in the db however:
Probability:
(How likely the bug is to happen, scored from 1-5. For example, probability of 5 is something like "it happens to all users every time they log in." whereas probability of 1 "only happens to certain users when a really specific and unlikely path is followed.")
Impact:
(How bad the bug is when it does happen, scored from 1-5. For example, effect of 5 is "the entire app crashes and makes it unusable for all users" or "the bug causes the wrong data to be saved, with critical information (e.g. payment) being affected." whereas effect of 1 is "It makes some styling look a little bit weird.")
Steps to reproduce the behaviour:
Screenshots:
Additional information:
OS: [e.g. iOS]
Browser: [e.g. chrome, safari]
Version: [e.g. 22]
Additional Context
The text was updated successfully, but these errors were encountered: