Version 28 (modified by Ryan J Ollos, 6 years ago) (diff)

News and release notes.

Autocomplete feature for the keywords field


The KeywordsSuggestPlugin provides an autocomplete function for the keywords ticket field or any other text-based ticket field. Optionally, it is possible to restrict the list of allowed keywords.

See also LoomingCloudsPlugin.

Bugs/Feature Requests


Version 0.5dev of this plugin is now available. Recent changes are:

  • Upgraded from the jQuery Autocomplete Plugin to jQuery UI 1.8.16.
  • Added support for the TagsPlugin (#4201).
  • The autocomplete list can be attached to a text-based field other than the Keywords field (#5831).
  • The helppage link can point to any resource in any realm. For example, it can be a link to the /tags page. Previously, it could only point to a wiki page (#5907).
  • Several bug fixes.

Compatibility notes:

  • Previously, the multipleseparator configuration option was defined in quotes (e.g. ", "). Now, only the separator character should be specified (e.g. multipleseparator = ,).
  • Several of the configuration options will be renamed before 0.5 is released. Please revisit this section for additional notes before installing a new version.

Planned enhancements before 0.5 is released:

  • Allow the autocomplete list to be attached to more than one text-based ticket field. Additionally, different configurations will be supported for each ticket field. For example, one of the ticket fields could be using keywords from the TagsPlugin and the other could be using keywords defined in trac.ini (#5831).
  • A new boolean option usetagsplugin. Currently, the TagsPlugin will be used when it is installed and enabled.
  • Offer all keywords used up until now for use, even if the TagsPlugin is not installed (#3816).

Existing bugs and feature requests for KeywordSuggestPlugin are here.

If you have any issues, create a new ticket.

Download and Source

Download the [download:keywordsuggestplugin zipped source], check out KeywordSuggestPlugin using Subversion, or browse the source with Trac.


Sample picture of autocomplete feature

The Keywords Label can be the link to a wiki page.

'helppage' option turned on


Following section must be added to trac.ini configuration file:

field = keywords
keywords = tag1,tag2,tag3
mustmatch = False
helppage = wiki/TicketKeywords
helppage.newwindow = False
matchcontains = True
multipleseparator = ,

There are two parameters to configure:

  • field - field to which the suggestion will be attached (default: keywords)
  • keywords - specifies list of comma separated values available for input
  • mustmatch - optional, if specified, 'keywords' field accepts values from the keywords list only
  • helppage - optional, if specified, 'keywords' label will be turned into the link to a resource. This could be a wiki page, or any resource in any realm, such as the tags page (helppage = tags).
  • helppage.newwindow - optional, whether wiki page opened in new window or not`
  • matchcontains - optional, whether keywords which matched not from the beginning must be included into list
  • multipleseparator - which character(s) is used as separator between keywords. Must be enclosed with quotas or other characters. If not specified, ', ' is used.

Recent Changes

16539 by rjollos on 2017-04-16 02:33:26
Fix indentation
15264 by rjollos on 2016-02-11 04:22:34
Remove unnecessary svn:mime-type on py files

svn:mime-type was set to "plain" for many files.

12103 by rjollos on 2012-10-03 05:38:09

Refs #8141:

  • Moved generation of keywords string into a private method.
  • Several other refactorings, backed by unit tests.
  • In Trac 1.0 and later, jQuery-UI from the Trac core is added to the page. The ability to add jQuery-UI to the page was added in Trac 1.0.


Author: scratcher
Maintainer: rjollos
Contributors: itamarost, falkb, hasienda

Attachments (2)

Download all attachments as: .zip