Dynamic client-side autocompletion features for the Apache Bloodhound ticket system

Apache Bloodhound is a software development collaboration tool, including issue tracking, wiki and repository browsing (see: http://bloodhound.apache.org). Bloodhound extends Trac (http://trac.edgewall.org/) with multiple product support, advanced search functionality, ticket relations, a simpler installer and sleeker user interface.

Problem:

The ticket system should assist the user when creating tickets in order to reduce typing and the potential for errors by autocompleting fields as the user types. For many ticket fields the appropriate entries are those that either have already been used or can be queried from the database.

Proposed solution:

Enhance Bloodhound with these features, implemented in Bootstrap and jQuery:

• Autocomplete the Owner and Cc fields from a list of valid users.
• Autocomplete keywords from a list of keywords that have been used to date.
• Search for duplicate tickets as the ticket summary is entered.

Ajax programming techniques will likely be utilized. A framework needs to be developed on the server-side in addition to the client-side features that are visible to the user. The possibility exists for identifying and proposing additional features to implement on the client-side.

Skills needed:

Bloodhound and Trac are written in Python, HTML and JavaScript, so a moderate dose of these programming skills are required.

References:

Links to the original issues:

https://issues.apache.org/bloodhound/ticket/185
https://issues.apache.org/bloodhound/ticket/233
https://issues.apache.org/bloodhound/ticket/765

More GSoC-related tasks for Bloodhound:

https://issues.apache.org/bloodhound/query?status=!closed&keywords=~gsoc

Guidelines for contributing to Apache Bloodhound:

https://issues.apache.org/bloodhound/wiki/BloodhoundContributing