Changing API Version should make it obvious to save filter before CI Job can be saved
It's a usability bug, I think.
When you change the API version in a CI Job, the button to save CI Job greys out but has a spinning dial of 'Something happening'. Actually the system is doing nothing, it is waiting for the filter to be saved (even if the filter wasn't saved before) but this is completely unclear.
Changes then
1. auto-save filter or bring up the 'save filter' modal
2. Show a toast message saying "save filter"
3. Button should grey out with hover text of "save filter", no spinner
I waited longer than I care to admit, hoping the button would un-grey itself
1
vote
Chester Hamilton
shared this idea
-
I can't upload a screenshot, but you edit settings on a CI Job > Metadata filters > API version dropdown, and change the value, and the Save CI Job shows a greyed spinner