community-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Peter Kozelj (JIRA)" <j...@apache.org>
Subject [jira] [Created] (COMDEV-96) [GSoC] Enhance ticket workflow customizations
Date Wed, 27 Mar 2013 07:15:16 GMT
Peter Kozelj created COMDEV-96:
----------------------------------

             Summary: [GSoC] Enhance ticket workflow customizations
                 Key: COMDEV-96
                 URL: https://issues.apache.org/jira/browse/COMDEV-96
             Project: Community Development
          Issue Type: New Feature
            Reporter: Peter Kozelj


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. Apache Bloodhound recently
graduated from the Apache Incubator as a stand-alone Apache project. 

Problem: 

Currently workflow can not be customized for different ticket types and is not easily editable
by project administrators that typical do not have direct access to config files and database.

Proposed solution: 

1. Add the ability to define different workflows per ticket type or optionally any other ticket
attribute.
2. Simple editor for ticket workflows for project and global admins or a more fancy graphical
WYSIWYG type of editor based on JavaScript if time permits

Skills needed: 

Bloodhound and Trac are written in Python, so a moderate dose of Python programing skills
are required. 

References: 

Link to the original issue: 

    https://issues.apache.org/bloodhound/ticket/485 

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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message