R
Richard Rein Jr
In the demo app, there are several different tag-related self-service actions ("Add Tags to ECR Repository", "Add Tags to SonarQube Project", "Add Tags to S3 Bucket"). Unfortunately, the existing solution leaves a bit to be desired:
  • Two of the examples use an object with key/value pairs, and the third (SonarQube) uses a string field expecting comma-delimited set of values
We have tried using an array field for adding tags to existing OpsGenie alerts, but that solution is a bit lacking as well:
  • With a generic field type of "array", the user is taken to a model in order to complete that field...and they must use JSON array syntax in order to provide a value
  • The field is not bound to anything, so there is no way to auto-complete any existing tags (potentially leading to many similar-but-different tags ending up getting persisted)
Similar to the tag input field used in systems like Stack Overflow, we would have use for a specific input field type for tags. Ideally, this new field type would simplify user input while also attempting to auto-complete with existing values (similar to a bound entity select field?), so that it is more obvious to a user when they are selecting an existing tag versus explicitly choosing to create a new one.