It’s a good use case to help us learn as a team !
For me a bug is “the system is supposed to work that way, and it doesn’t”. It if was badly designed but work as expected, this is not a bug.
How is the system supposed to work ?
For a given customer:
- If there is only one OC, the user is not asked to choose, the active OC directly displays. The selector dropdown is still visible though, but with nothing to choose from. So @Kirsten I disagree with your interpretation of how the system is supposed to work as it already doesn’t ask to choose if only one OC
- If there is more than one OC, the user is asked to choose before the content of the shop displays.
As I don’t know the case of tagged customer were included and we have not way to really know it, I would say that:
- displaying automatically the content of the shop if a tagged customer has access to only one OC is the way the feature was designed to work, so maybe we forgot to test that case, but it is a bug if we refer to how the feature is supposed to work
- not proposing a dropdown with choosing option is there is only one option is bad design but not a bug, so it’s a new feature type “UX improvement to reduce confusion for OC selection”
if we forget a test case and release a feature that is nos working as expected because of that, it should be bug no ? Or we can decide afterwards to rescope the feature that was released… and then decide to treat as a new feature the thing that is not working yet. I guess it’s a case based decision @Rachel ?
Would be good to have @danielle opinion on this so we right down some rule for such case and know how to treat them ?