To reproduce, click the + in the tags column in one any of the resource tables. In the dialog box, enter a new tag name and click the + to add it.
Two problems:
- the tag schema doesn't have
group as a required field. Fixing this will resolve the 500 error and correctly raise a 400 error.
- the UI isn't sending the
group. The correct value is the group of the resource being tagged.
NOTE: I observed this issue on dev, but I have multiple groups in my database. It's possible the UI part of this issue is affected by this (e.g. it is defaulting the group if only one is available). If so, the second part of this fix could potentially wait until group creation is implemented.