[Apache Bloodhound] Proposals/BEP-0013 modified
Page Proposals/BEP-0013 was changed by thimal Diff URL: https://issues.apache.org/bloodhound/wiki/Proposals/BEP-0013?action=diffversion=4 Revision 4 Changes: ---8--8--8--8--8--8--8--8 Index: Proposals/BEP-0013 = --- Proposals/BEP-0013 (version: 3) +++ Proposals/BEP-0013 (version: 4) @@ -80,7 +80,9 @@ This will show list of related tickets to users to avoid duplicates. -For this it need to use the BloodhoundSearch API, But due to the complexity in powerfulness of BloodhoundSearch API I hope to start with the TracSearch API and get the component to work with the TracSearch API and then move into the BloodhoundSearch API, as a incremental development. (need to check the possibility to use the Query API, I have not done many research on this so need to do bit research on this). +This has two approaches first is to use the Ticket Query API, other one is to use the BloodhoundSearch API. +But to give more support to users to find the duplicate ticket it need to search whole phrase typed in the summary field, part of the phrase typed in summary field and significant words typed in summary field. To search all these at once it is better to use BloodhoundSearch API. As the Ticket Query API search only the exact phrase or word provide to it. (but need to check the performance) +For this it need to use the BloodhoundSearch API, But due to the complexity in powerfulness of BloodhoundSearch API I hope to start with the TracSearch API and get the component to work with the TracSearch API and then move into the BloodhoundSearch API, as a incremental development. @@ -93,7 +95,7 @@ For the frond end it has two fields to update. Cc field would be same as the keyword field and owner field will give list of users according to the keys users type and only username can enter. -== Approximate Schedule #Approximate Schedule +== Approximate Schedule #Approximate Schedule Gsoc will be for 14 weeks and here is rough estimation of the work break down. But this will be change according to the work flow and the discussion with bloodhound community. ---8--8--8--8--8--8--8--8 -- Page URL: https://issues.apache.org/bloodhound/wiki/Proposals/BEP-0013 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound issue tracker This is an automated message. Someone added your email address to be notified of changes on 'Proposals/BEP-0013' page. If it was not you, please report to .
[Apache Bloodhound] Proposals/BEP-0015 modified
Page Proposals/BEP-0015 was changed by devenderbindal Diff URL: https://issues.apache.org/bloodhound/wiki/Proposals/BEP-0015?action=diffversion=3 Revision 3 Changes: ---8--8--8--8--8--8--8--8 Index: Proposals/BEP-0015 = --- Proposals/BEP-0015 (version: 2) +++ Proposals/BEP-0015 (version: 3) @@ -22,13 +22,24 @@ == Motivation == -After adding this calendar views. By this user can see the schedule of upcoming work and can also schedule work by interacting with it. It will make the user task easy. +1. After adding this calendar views. By this user can see the schedule of upcoming work and can also schedule work by interacting with it. It will make the user task easy. == Proposal #proposal 2. Important Features, Approach and Detailed Description 2.1 Add Basic feature of month-long calendar view, showing the due date for milestone and tickets. +2.2 Add Several filters like filter by user, milestone, open/close ticket, sort by priority asc/desc, reopened, status, assigned. +2.3 Scale it to week, month and year views. +2.4 Add Drag and drop feature for the schedule ticket onto the calendar view. +2.5 Allow the calendar to be annotated with arbitrary notes/events feature which save the notes/events in different color than ticket. +2.6 Extend it to work with various scopes, not only with milestone. +2.7 Embed it in the query and milestone pages. +2.8 If time allows, Google Calendar Plugin. + +== Rationale #rationale + +2.1 Add Basic feature of month-long calendar view, showing the due date for milestone and tickets. This will initially start by using the trac ticket calender plugin(1) which contains the basic month view. It also contains the list view which can also be utilized. It is in python, so can easily be integrated in bloodhound. @@ -74,51 +85,128 @@ It will allow a user of Google Calendar to subscribe to the Bloodhound calendar. Google calendar uses the iCAL format. Any other users can also subscribe to it provided there calendar uses the iCAL format. -== Rationale #rationale - -The rationale fleshes out the specification by describing what motivated the design and why particular design decisions were made. It should describe alternate designs that were considered and related work, e.g. how the feature is supported in other issue trackers or ''Trac'' hacks . The rationale should provide evidence of consensus within the community and discuss important objections or concerns raised during discussion. Take a look at sample rationale below - -''BEP'' submissions come in a wide variety of forms, not all adhering to the format guidelines set forth below. Use this template, in conjunction with the [wiki:/Proposals general content guidelines] and the [wiki:/Proposals/Formats/WikiFormatting WikiFormatting BEP guidelines], to ensure that your ''BEP'' submission is easy to read and understand. - -This template allows to create BEPs and is very similar to [http://www.python.org/dev/peps/pep-0012 PEP 12] . However it has been optimized by moving long explanations to the [wiki:/Proposals/Formats/WikiFormatting WikiFormatting BEP guidelines] . If you are interested take a look at the [?action=diffold_version=1 differences]. The goal is to redact new BEPs just by following in-line instructions between angle brackets (i.e. ) . Even if this will allow to write BEPs faster , it is highly recommended to read the [wiki:/Proposals/Formats/WikiFormatting WikiFormatting BEP guidelines] at least once in your lifetime to be aware of good practices and expected style rules . - -== How to Use This Template #howto - -BEPs may include further sections. This is an example. - -Quick edits will consist in following the instructions inside angle brackets (i.e. ) . That should be everything needed to write new BEPs. To be more informed about advanced considerations please read the [wiki:/Proposals general content guidelines] and the [wiki:/Proposals/Formats/WikiFormatting WikiFormatting BEP guidelines] . If there is no point in including one of the sections in this document then feel free to remove it. - -== Backwards Compatibility #backwards-compatibility - -All BEPs that introduce backwards incompatibilities must include a section describing these incompatibilities and their severity. The ''BEP'' must explain how to deal with these incompatibilities. ''BEP'' submissions without a sufficient backwards compatibility treatise may be rejected outright. - -== Reference Implementation #reference-implementation - - The reference implementation **must** be completed before any ''BEP'' is given status **Final**, but it need not be completed before the ''BEP'' is accepted. It is better to finish the specification and rationale first and reach consensus on it before writing code. The final implementation **must** include test code and documentation
[Apache Bloodhound] Proposals/BEP-0015 modified
Page Proposals/BEP-0015 was changed by devenderbindal Diff URL: https://issues.apache.org/bloodhound/wiki/Proposals/BEP-0015?action=diffversion=5 Revision 5 Changes: ---8--8--8--8--8--8--8--8 Index: Proposals/BEP-0015 = --- Proposals/BEP-0015 (version: 4) +++ Proposals/BEP-0015 (version: 5) @@ -56,7 +56,7 @@ 2.3 Scale it to week, month and year views. -This feature will initially start by using the trac week plan plugin(2). I can extend this plugin to the month calender as sub plugin and I can create the year plugin similarly as well. So, It will be like calender view containing three view: year, month, and week with month view as default. This plugin uses the jquery plugin named FullCalender(3). +This feature will initially start by using the trac week plan plugin(2). I can extend this plugin to the month calender as sub plugin and I can create the year plugin similarly as well. So, It will be like calender view containing three view: year, month, and week with month view as default. This plugin uses the jquery plugin named FullCalendar (3). 2.4 Add Drag and drop feature for the schedule ticket onto the calendar view. ---8--8--8--8--8--8--8--8 -- Page URL: https://issues.apache.org/bloodhound/wiki/Proposals/BEP-0015 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound issue tracker This is an automated message. Someone added your email address to be notified of changes on 'Proposals/BEP-0015' page. If it was not you, please report to .
Re: [Apache Bloodhound] #777: User restriction to only tickets they open?
#777: User restriction to only tickets they open? --+ Reporter: mbrownnyc| Owner: nobody Type: enhancement | Status: new Priority: major| Milestone: Component: dashboard|Version: Resolution: | Keywords: --+ Comment (by gjm): Actually I am still not entirely happy with the result but mostly because of trac:#7608 which I think means that the tickets will still be visible in queries and will also spoil the previous and next ticket links. -- Ticket URL: https://issues.apache.org/bloodhound/ticket/777#comment:7 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound issue tracker
Re: [Apache Bloodhound] #570: Bootstrap template for product_edit.html
#570: Bootstrap template for product_edit.html --+--- Reporter: rjollos | Owner: nobody Type: enhancement | Status: new Priority: major| Milestone: next 0.x Component: ui design|Version: Resolution: | Keywords: starter bootstrap --+--- Comment (by devenderbindal): Patch submitted at github(1) (1) https://github.com/dev9226134/bloodhound/commit/f65e96c8cffc0db7e813c18b404220a0037f -- Ticket URL: https://issues.apache.org/bloodhound/ticket/570#comment:6 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound issue tracker
Re: [Apache Bloodhound] #570: Bootstrap template for product_edit.html
#570: Bootstrap template for product_edit.html --+--- Reporter: rjollos | Owner: rjollos Type: enhancement | Status: accepted Priority: major| Milestone: Release 8 Component: ui design|Version: Resolution: | Keywords: starter bootstrap --+--- Changes (by rjollos): * owner: nobody = rjollos * status: new = accepted * milestone: next 0.x = Release 8 -- Ticket URL: https://issues.apache.org/bloodhound/ticket/570#comment:7 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound issue tracker
Re: [Apache Bloodhound] #792: Invalid search result after moving ticket to another product
#792: Invalid search result after moving ticket to another product ---+-- Reporter: olemis| Owner: nobody Type: defect| Status: new Priority: critical | Milestone: next 0.x Component: search|Version: 0.8.0dev Resolution:| Keywords: ticket batch modify, product ---+-- Comment (by olemis): Replying to [comment:5 olemis]: Replying to [comment:3 rjollos]: [...] and I wonder if we have really implemented support to move tickets, If we haven't then we should do it rather than removing this feature from batch modify form . IMHO , support has been added but not all the implications of this action have been identified , implemented , polished and tested . So it's correct to think that , at some extent , «it just sort of works by chance» , but IMO the approach looking forward should be to improve what we have rather than remove this feature . [...] -- Ticket URL: https://issues.apache.org/bloodhound/ticket/792#comment:6 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound issue tracker
[Apache Bloodhound] Proposals/BEP-0012 modified
Page Proposals/BEP-0012 was changed by sifa_sensay
Diff URL:
https://issues.apache.org/bloodhound/wiki/Proposals/BEP-0012?action=diffversion=13
Revision 13
Changes:
---8--8--8--8--8--8--8--8
Index: Proposals/BEP-0012
=
--- Proposals/BEP-0012 (version: 12)
+++ Proposals/BEP-0012 (version: 13)
@@ -24,26 +24,36 @@
== Proposal #proposal
The implementation of the project can be splitted into three distinct parts,
the keyword and user suggestion components, and duplicate ticket search
component.
-The keyword suggestion component of the project will suggest entries that are
used in existing tickets while user suggestion component will autocomplete the
Owner and Cc fields from a list of valid users. Pressing the down key will be
sufficient to display suggested keywords in an alphabetical list that the user
can scroll through. Instead of an alphabetical order, popularity of entries
would be used to order the suggested keywords and also matching would not be
case sensitive to give more flexibility to the user in typing.
+The keyword suggestion component of the project will suggest entries that are
used in existing tickets while user suggestion component will autocomplete the
Owner and Cc fields from a list of valid users. Detecting left mouse button
press in the search field will be sufficient to display suggested keywords in
an alphabetical list that the user can scroll through. Instead of an
alphabetical order, popularity of entries (i.e. frequency of keywords) would be
used to order the suggested keywords and also matching would not be case
sensitive to give more flexibility to the user in typing. This would be
implemented simply by converting the user’s entry to lowercase letter before
looking for suggestions.
+
+Detecting left mouse button press would be implemented in JQuery by
mousedown() function. For instance,
+
+$('#mousedown').mousedown(function(){
+ //list keywords in an alphabetical order
+});
+
+ would be an example of how the detecting left mouse button press code will
look like.
+
+Popularity of entries would be implemented by storing the keywords and their
frequencies in a table in the database. In more detail, we will create a table
in the database with all possible suggestions (and will create another table
for all possible usernames), all starts with zero frequency and then when user
searches for a keyword/username, we will increase the frequency of that
specific word in the database. We will suggest keywords/usernames in an
alphabetical order, until we have useful frequency results.
The keyword and user suggestion component of the project will be coded using
jQuery (JavaScript library). Since most of Bloodhound’s design is done using
the Twitter Bootstrap framework, the autocompletion part of the code can also
be designed using Twitter Bootstrap Typeahead plugin.
-
Suggestions can be stored into the source array and can be retrieved on page
load. However, this is really inefficient when there are thousands of
keywords/usernames since user needs to wait for a long time for the page to be
displayed. Alternative solution to this would be storing the suggestions in
dynamically retrieved server-side (i.e. database), which will provide faster
and more efficient results. More advanced approach would be using the
dynamically retrieved server-side with a JSON format (JavaScript Object
Notation) for human-readable data interchange between client and server.
Using dynamically retrieved server-side for retrieving the suggestions will be
faster. However, there will be some latency in retrieving the possible
keywords/usernames. In order to overcome the latency, AJAX (Asynchronous
JavaScript And XML) would be used to leave client active while the server
retrieves the keywords/usernames.
The duplicate ticket search component of the project will assist the user to
search for the duplicate tickets when entering a new ticket’s summary. One of
the possible solution would be determining the duplicates by searching the
summary of existing tickets whereas searching the ticket description would be
better and powerful solution.
-
The duplicate ticket search part of the project will be coded using
jQuery and AJAX. Since most of Bloodhound’s design has been done using the
Twitter Bootstrap framework, this part of the code can also be designed using
Twitter Bootstrap. First, the duplicate search feature will be implemented to
work with the Trac Search API then it will be manipulated to work with the
BloodhoundSearchPlugin since it is much more powerful than Trac Search API.
However, the ticket Query API would be another solution to implement duplicate
search feature rather than interacting with Search components. The ticket Query
API has support for searching ticket summaries and descriptions that contain
words and phrases.
[Apache Bloodhound] Proposals/BEP-0015 modified
Page Proposals/BEP-0015 was changed by devenderbindal Diff URL: https://issues.apache.org/bloodhound/wiki/Proposals/BEP-0015?action=diffversion=8 Revision 8 Changes: ---8--8--8--8--8--8--8--8 Index: Proposals/BEP-0015 = --- Proposals/BEP-0015 (version: 7) +++ Proposals/BEP-0015 (version: 8) @@ -90,7 +90,7 @@ 2.8 If time allows, Google Calendar Plugin. -It will allow a user of Google Calendar to subscribe to the Bloodhound calendar. Google calendar uses the iCAL format. Any other users can also subscribe to it provided there calendar uses the iCAL format. +I will implement the iCal support, which will allow Google Calendar to subscribe to to the Bloodhound Calendar. == Timeline #Timeline ---8--8--8--8--8--8--8--8 -- Page URL: https://issues.apache.org/bloodhound/wiki/Proposals/BEP-0015 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound issue tracker This is an automated message. Someone added your email address to be notified of changes on 'Proposals/BEP-0015' page. If it was not you, please report to .
