Details
-
Type: Bug
-
Status: Won't Do
-
Priority: Important
-
Resolution: Won't Do
-
Affects Version/s: 4.7.24
-
Fix Version/s: None
-
Component/s: Core CiviCRM
-
Labels:None
-
Versioning Impact:Patch (backwards-compatible bug fixes)
-
Documentation Required?:None
-
Funding Source:Needs Funding
-
Verified?:No
Description
An authorised user should be able to see all of the tags included in a given tagset. However, certainly in terms of tags used for contacts (I've not tested other types of tags) this is not the case. When editing a contact record, in the 'Tags and Groups' pane the user can see a multi-select field for Groups, and what appears to be a similar multi-select field for any tagset/s that are created. Clicking into the Groups field, the list of Groups immediately becomes available, and the user can scroll through this list to find the required group/s, and/or they can begin keying the name of the required group to shorted the list and make their selection.
The same approach should be true for tagsets. However, when clicking into a tagset field, all the user sees is the text "enter search term" - no tags become apparent until they begin keying characters, and then of course only those tags that match the keyed characters are presented. Consequently users have no way of accessing a complete list of available tags in the tagset, and must learn all the tags or have a 'cheat sheet' available to them.
As I can't conceive of any rational use case where a user with full admin permissions would not be able to view the list of tags as a drop-down, as is the case with groups, I must therefore assume that this is an error or a bug.
I found this behaviour on a fresh Wordpress install, and was able to replicate it on the http://dmaster.demo.civicrm.org site.
The desired behaviour for tagset fields is identical the that which we currently see for other conventional multi-select fields used in CiviCRM, e/g/ the groups field as noted above.
For me the current behaviour pretty much renders tagsets useless.