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
Right now, the tags multi-select field in ticket documents uses a tagPicker input component to load its tag options dynamically via the tagOption document type. It stores the user selection in an array of strings, which means tags are not directly linked to tag options, and therefore:
When a user renames a tag option, tickets' tags arrays do not automatically update
It is unnecessarily difficult to query tickets by tag
If we make tags an array of references and adapt tagPicker to work with references instead, the above issues are resolved. It also reduces the confusion around having a tag object and a tagOptions document, leaving only the need for one of them.
Also, this will make the tagPicker more robust in case we want to publish a version of it as a multi-select input plugin.
The text was updated successfully, but these errors were encountered:
Right now, the
tags
multi-select field inticket
documents uses atagPicker
input component to load its tag options dynamically via thetagOption
document type. It stores the user selection in an array of strings, which means tags are not directly linked to tag options, and therefore:tags
arrays do not automatically updateIf we make
tags
an array of references and adapttagPicker
to work with references instead, the above issues are resolved. It also reduces the confusion around having atag
object and atagOptions
document, leaving only the need for one of them.Also, this will make the
tagPicker
more robust in case we want to publish a version of it as a multi-select input plugin.The text was updated successfully, but these errors were encountered: