Formalize and optimize autocomplete of issue tags *in the issue metadata form* [#2418255]

Followup to #2362065: Sort autocomplete of issue tags descending by usage count *in the issue metadata form*:

Problem/Motivation

Certain issue tags are well-known and should be preferred for auto-completion.

Proposed resolution

Give the highest priority to "official" issue tags.

The suggested way to do this (this will save you having to read the other issue):

Formalize the official tag list, cache it, and have an ultra-fast autocomplete of preferred tags. It could even be two-step, returning the fast preferred results first and then the deeper search later.
Add a boolean field to the tags taxonomy to achieve this.

Remaining tasks

To work on the d.o server

server: tags-drupal.redesign.devdrupal.org
get access: username: drupal password: drupal
to be able to edit a issue (see the autocomplete tag): username: bacon password bacon
sample issue: https://tags-drupal.redesign.devdrupal.org/node/2380883

Handbook page for working on d.o: Develop on our server (preferred) https://www.drupal.org/node/1018084

User interface changes

API changes

Comments

Comment #1

cilefen CreditAttribution: cilefen commented 1 February 2015 at 22:19

Issue summary:

View changes

Comment #2

joachim CreditAttribution: joachim commented 2 February 2015 at 09:48

> Two ideas were offered (this will save you having to read the other issue):..,.

I don't think those are two separate ideas.

Rather, 'Add a boolean field to the tags taxonomy' is what I suggested as the way to mark which tags are official. The system that caches that list would query based on that boolean field.

Comment #3

cilefen CreditAttribution: cilefen commented 5 February 2015 at 15:53

Issue summary:

View changes

@joachim Right - I reworded the summary.

Comment #4

YesCT CreditAttribution: YesCT commented 5 February 2015 at 15:57

#2013222: Add "Issue tasks" to project issues and correlate tasks with handbook documentation
has background about configuring "official" tags per project.

Comment #5

cilefen CreditAttribution: cilefen commented 5 February 2015 at 16:01

Status:

Needs work

» Postponed

Postponed on #2362065: Sort autocomplete of issue tags descending by usage count *in the issue metadata form*

Comment #6

drumm

he/him

NY, US

CreditAttribution: drumm commented 9 February 2015 at 23:31

Add a boolean field to the tags taxonomy to achieve this

A text field or area might be better for making tags official. If the text is empty, it is not official. If the text is not empty, that official tag has a bit of description that can be used for a bit of instruction on #2013222: Add "Issue tasks" to project issues and correlate tasks with handbook documentation. And/or the field could be a link/reference field to the handbook page about the tag.