Using the Assign Tag > More option in a list view will create a new tag using the sys_id of the tag they selectedDescriptionIf a user has many tags and uses the Assign Tag > More option on a list view, this does not apply the tag they selected. Instead, a new tag is created for the user. The name of this new tag is the sys_id of the tag the user selected. Note that this only occurs for tags that are specific to Users/Groups. Tags with visibility set to Everyone do not exhibit the behavior.Steps to Reproduce 1) Download the label xml attached to this PRB and import it into the instance. This xml contains several test labels so you do not have to create them all yourself.2) Impersonate the Itil user3) Navigate to incident.list4) Personalize the list and add the Tags column so that you can observe the issue5) Click the checkbox next to an incident in the list6) In the "Actions on selected rows..." dropdown, select: Assign Tag > More... (note, the More option will not be available if an incident on the list has a tag applied, this is another issue)7) In the assign tag popup, type: Group Tag Test and press OK to confirm the selection8) Right-click the list header and choose: Refresh List9) When the list refreshes, find the incident you assigned the tag to and notice the tag displays a sys_id. If you navigate to Self Service > My Tags, you will see the sys_id tag was created for the itil userThe tag the user selects does not get applied to the incident, instead a new tag is created and given the name of the selected tag's sys_id.WorkaroundThis problem has been fixed in Orlando. There is no workaround available.Related Problem: PRB1382307