Return-Path: X-Original-To: apmail-community-commits-archive@minotaur.apache.org Delivered-To: apmail-community-commits-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id ACF821074A for ; Mon, 24 Feb 2014 21:37:40 +0000 (UTC) Received: (qmail 15851 invoked by uid 500); 24 Feb 2014 21:37:26 -0000 Delivered-To: apmail-community-commits-archive@community.apache.org Received: (qmail 15666 invoked by uid 500); 24 Feb 2014 21:37:23 -0000 Mailing-List: contact commits-help@community.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@community.apache.org Delivered-To: mailing list commits@community.apache.org Received: (qmail 15498 invoked by uid 99); 24 Feb 2014 21:37:20 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 24 Feb 2014 21:37:20 +0000 Date: Mon, 24 Feb 2014 21:37:20 +0000 (UTC) From: "Ryan J Ollos (JIRA)" To: commits@community.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (COMDEV-111) Dynamic client-side autocompletion features for the Apache Bloodhound ticket system MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/COMDEV-111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ryan J Ollos updated COMDEV-111: -------------------------------- Description: 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 was: 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. 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 > Dynamic client-side autocompletion features for the Apache Bloodhound ticket system > ----------------------------------------------------------------------------------- > > Key: COMDEV-111 > URL: https://issues.apache.org/jira/browse/COMDEV-111 > Project: Community Development > Issue Type: New Feature > Components: Comdev > Reporter: Ryan J Ollos > Labels: AJAX, HTML, JavaScript, Python, bloodhound, gsoc2014 > > 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 -- This message was sent by Atlassian JIRA (v6.1.5#6160)