[Apache Bloodhound] New user registration: cgraff
New user registration for user cgraff -- Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound issue tracker
[Apache Bloodhound] #616: Component with umlauts destroys milestone view (Http 500)
#616: Component with umlauts destroys milestone view (Http 500)
---+
Reporter: cgraff | Owner: nobody
Type: defect | Status: new
Priority: major | Milestone:
Component: dashboard |Version: 0.6.0
Keywords: |
---+
By using a project component containing an umlaut the milestone view will
not be shown anymore. The page then displays a Genshi error.
The log file says the following:
{{{
2013-07-30 08:45:14,105 Trac[main] WARNING: [127.0.0.1] HTTPInternalError:
500 Trac Error (Genshi UnicodeEncodeError error while rendering template
(unknown template location))
}}}
=== Steps to reproduce ===
1. in your project create a component containing an umlaut
2. create a milestone
3. create a ticket and
4. choose the component that contains the umlaut for this ticket
5. assign this ticket to the milestone created before
6. view the milestone
=== Notes ===
Replacing the component's umlaut by an ''undangeours'' representation
(e.g. ü - ue) leads to a successful view of the milestone.
--
Ticket URL: https://issues.apache.org/bloodhound/ticket/616
Apache Bloodhound https://issues.apache.org/bloodhound/
The Apache Bloodhound issue tracker
Re: [Apache Bloodhound] #616: Component with umlauts destroys milestone view (Http 500)
#616: Component with umlauts destroys milestone view (Http 500) +--- Reporter: cgraff | Owner: nobody Type: defect | Status: new Priority: major | Milestone: Release 7 Component: dashboard |Version: 0.6.0 Resolution: | Keywords: +--- Changes (by rjollos): * milestone: = Release 7 Comment: Confirmed. Thank you for the report. -- Ticket URL: https://issues.apache.org/bloodhound/ticket/616#comment:1 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound issue tracker
svn commit: r1508449 - /bloodhound/trunk/bloodhound_dashboard/bhdashboard/widgets/ticket.py
Author: rjollos Date: Tue Jul 30 14:00:03 2013 New Revision: 1508449 URL: http://svn.apache.org/r1508449 Log: Fix for components with unicode characters preventing rendering of the milestone view. Fixes #616. The milestone view shows a list of components, and the milestone view would not render due to an improperly encoded href string. URL encoding of the query href parameters did not account for the possibility that the parameters could be unicode strings. Modified: bloodhound/trunk/bloodhound_dashboard/bhdashboard/widgets/ticket.py Modified: bloodhound/trunk/bloodhound_dashboard/bhdashboard/widgets/ticket.py URL: http://svn.apache.org/viewvc/bloodhound/trunk/bloodhound_dashboard/bhdashboard/widgets/ticket.py?rev=1508449r1=1508448r2=1508449view=diff == --- bloodhound/trunk/bloodhound_dashboard/bhdashboard/widgets/ticket.py (original) +++ bloodhound/trunk/bloodhound_dashboard/bhdashboard/widgets/ticket.py Tue Jul 30 14:00:03 2013 @@ -34,6 +34,7 @@ from trac.ticket.api import TicketSystem from trac.ticket.query import Query from trac.ticket.roadmap import apply_ticket_permissions, get_ticket_stats, \ ITicketGroupStatsProvider, RoadmapModule +from trac.util.text import unicode_urlencode from trac.util.translation import _ from trac.web.chrome import add_stylesheet @@ -217,7 +218,7 @@ class TicketFieldValuesWidget(WidgetBase query_href = query.get_href(req.href) item_link= lambda item: query_href + \ -'' + urlencode([(fieldnm, item[0])]) +'' + unicode_urlencode([(fieldnm, item[0])]) if fieldnm in self.DASH_ITEM_HREF_MAP: def dash_item_link(item):
Re: [Apache Bloodhound] #616: Component with umlauts destroys milestone view (Http 500)
#616: Component with umlauts destroys milestone view (Http 500) +--- Reporter: cgraff | Owner: rjollos Type: defect | Status: assigned Priority: major | Milestone: Release 7 Component: ui design |Version: 0.6.0 Resolution: | Keywords: +--- Changes (by rjollos): * status: new = assigned * owner: nobody = rjollos * component: dashboard = ui design Comment: (In [1508449]) Fix for components with unicode characters preventing rendering of the milestone view. Fixes #616. The milestone view shows a list of components, and the milestone view would not render due to an improperly encoded href string. URL encoding of the query href parameters did not account for the possibility that the parameters could be unicode strings. -- Ticket URL: https://issues.apache.org/bloodhound/ticket/616#comment:2 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound issue tracker
Re: [Apache Bloodhound] #616: Component with umlauts destroys milestone view (Http 500)
#616: Component with umlauts destroys milestone view (Http 500) +--- Reporter: cgraff | Owner: rjollos Type: defect | Status: closed Priority: major | Milestone: Release 7 Component: ui design |Version: 0.6.0 Resolution: fixed | Keywords: +--- Changes (by rjollos): * status: assigned = closed * resolution: = fixed -- Ticket URL: https://issues.apache.org/bloodhound/ticket/616#comment:3 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound issue tracker
[Apache Bloodhound] Proposals/BEP-0007 modified
Page Proposals/BEP-0007 was changed by antonia.horincar Diff URL: https://issues.apache.org/bloodhound/wiki/Proposals/BEP-0007?action=diffversion=5 Revision 5 Changes: ---8--8--8--8--8--8--8--8 Index: Proposals/BEP-0007 = --- Proposals/BEP-0007 (version: 4) +++ Proposals/BEP-0007 (version: 5) @@ -97,6 +97,29 @@ '''Current state of the implementation:''' At this point the API can retrieve information about tickets, milestones and products. It can also retrieve information about queries, but not for all the cases (there are some cases when the API fails to correctly retrieve query results, therefore this part is still being worked on). + +'''Timeline:''' + +May 27 - June 17 +- Collaborate with the community in Bloodhound’s mailing list to get a more in depth understanding of the modules, classes and interfaces existing in Bloodhound + +June 17 - July 29 +- Develop the REST API for interacting with objects from external sources: +- Implement a class which retrieves information about Bloodhound objects +- Develop unit tests where appropriate + +''Midterm Evaluation'' + +July 29 - September 15 +- Finish implementing the back end part and add more tests +- Develop the !JavaScript API for generating HTML snippets, along with the user interface + +September 15 - September 23 +- Refactor code, finish tests and documentation + +''Final evaluation'' + + == Resources #resources ---8--8--8--8--8--8--8--8 -- Page URL: https://issues.apache.org/bloodhound/wiki/Proposals/BEP-0007 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-0007' page. If it was not you, please report to .
[Apache Bloodhound] #617: Switching from QCT to full dialogue loses field values
#617: Switching from QCT to full dialogue loses field values -+--- Reporter: mudri |Owner: Type: defect | Status: new Priority: major | Version: Resolution: | -+--- Anything written in the Create Ticket dropdown is lost when More fields is clicked. The values in the fields should be posted through to the /newticket page, but instead are discarded. -- Ticket URL: https://issues.apache.org/bloodhound/ticket/617 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound issue tracker
Re: [Apache Bloodhound] #617: Switching from QCT to full create ticket page loses field values
#617: Switching from QCT to full create ticket page loses field values + Reporter: mudri | Owner: nobody Type: defect | Status: new Priority: major | Milestone: Component: ui design |Version: Resolution: | Keywords: + Changes (by mudri): * component: dashboard = ui design -- Ticket URL: https://issues.apache.org/bloodhound/ticket/617#comment:2 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound issue tracker
Re: [Apache Bloodhound] #618: Parent/child updates for QCT select /
#618: Parent/child updates for QCT select / --+--- Reporter: olemis | Owner: nobody Type: enhancement | Status: new Priority: major| Milestone: Component: ui design|Version: 0.6.0 Resolution: | Keywords: qct ticket fields --+--- Changes (by olemis): * keywords: = qct ticket fields * owner: = nobody * component: = ui design Old description: There's something wrong with quick ticket user experience once multi- product support is installed in place . The fact is that QCT will display field values for the current (product/global) context . If a ticket is created for a different product the set of components / versions / milestones / ... will not be the same . This might lead to one of (at least) three cases . 1. missing value UI due to resource name mismatch 2. wrong/invalid field value reflected in UI , in cases where field value is shown anyway even on mismatch 3. Trac errors e.g. resource not found New description: There's something wrong with quick ticket user experience once multi- product support is installed in place . The fact is that QCT will display field values for the current (product/global) context . If a ticket is created for a different product the set of components / versions / milestones / ... will not be the same . This might lead to one of (at least) three cases . 1. missing value UI due to resource name mismatch 2. wrong/invalid field value reflected in UI , in cases where field value is shown anyway even on mismatch 3. Trac errors e.g. resource not found -- -- Ticket URL: https://issues.apache.org/bloodhound/ticket/618#comment:1 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound issue tracker
Re: [Apache Bloodhound] #618: Parent/child updates for QCT select /
#618: Parent/child updates for QCT select / --+--- Reporter: olemis | Owner: nobody Type: enhancement | Status: new Priority: major| Milestone: Component: ui design|Version: 0.6.0 Resolution: | Keywords: qct ticket fields --+--- Description changed by olemis: Old description: There's something wrong with quick ticket user experience once multi- product support is installed in place . The fact is that QCT will display field values for the current (product/global) context . If a ticket is created for a different product the set of components / versions / milestones / ... will not be the same . This might lead to one of (at least) three cases . 1. missing value UI due to resource name mismatch 2. wrong/invalid field value reflected in UI , in cases where field value is shown anyway even on mismatch 3. Trac errors e.g. resource not found New description: There's something wrong with quick ticket user experience once multi- product support is installed in place . The fact is that QCT will display field values for the current (product/global) context . If a ticket is created for a different product the set of components / versions / milestones / ... will not be the same . This might lead to one of (at least) three cases . 1. missing value in UI due to resource name mismatch 2. wrong/invalid field value reflected in UI , in case it is shown anyway even on mismatch 3. Trac errors e.g. resource not found -- -- Ticket URL: https://issues.apache.org/bloodhound/ticket/618#comment:2 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound issue tracker
[Apache Bloodhound] Proposals/BEP-0008 modified
Page Proposals/BEP-0008 was changed by huaxiang Diff URL: https://issues.apache.org/bloodhound/wiki/Proposals/BEP-0008?action=diffversion=6 Revision 6 Changes: ---8--8--8--8--8--8--8--8 Index: Proposals/BEP-0008 = --- Proposals/BEP-0008 (version: 5) +++ Proposals/BEP-0008 (version: 6) @@ -32,6 +32,15 @@ Proposed solution: · Take snaps to keep the changes of statuses and the time those occurred. · Use data mining tools to find some patterns, generate time series reports. + + == Implementation +* Generate no-graphic time series reports: + This function could be simply added into existing reports page. Basically, columns from ticket and ticket_change tables would be retrieved. The 'time' column from ticket_change table is the time point when tickets changes occurred. + In order to provide correct time format, a new field named 'tctime' added into trac\trac\ticket\api.py. Relevant files were updated as well. + Devs also suggested the code would be structured in a plugin. + +* Generate graphic time series reports: + One option is using js. == Progress * Spot methods/functions can be used to generate time-series report. (Done by early July) ---8--8--8--8--8--8--8--8 -- Page URL: https://issues.apache.org/bloodhound/wiki/Proposals/BEP-0008 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-0008' page. If it was not you, please report to .
[Apache Bloodhound] Proposals/BEP-0008 modified
Page Proposals/BEP-0008 was changed by huaxiang Diff URL: https://issues.apache.org/bloodhound/wiki/Proposals/BEP-0008?action=diffversion=8 Revision 8 Changes: ---8--8--8--8--8--8--8--8 Index: Proposals/BEP-0008 = --- Proposals/BEP-0008 (version: 7) +++ Proposals/BEP-0008 (version: 8) @@ -37,9 +37,9 @@ == Implementation #implementation * Generate no-graphic time series reports: - This function could be simply added into existing reports page. Basically, columns from ticket and ticket_change tables would be retrieved. The 'time' column from ticket_change table is the time point when tickets changes occurred. + At the first stage, this function could be simply added into existing reports page. Basically, columns from ticket and ticket_change tables would be retrieved. The 'time' column from ticket_change table records the time points when tickets changes occurred. In order to provide correct time format, a new field named 'tctime' added into trac\trac\ticket\api.py. Relevant files were updated as well. - Devs also suggested the code would be structured in a plugin. + Devs also suggested the code would be structured in a plugin rather than integrated into bloodhound. * Generate graphic time series reports: One option is using js. ---8--8--8--8--8--8--8--8 -- Page URL: https://issues.apache.org/bloodhound/wiki/Proposals/BEP-0008 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-0008' page. If it was not you, please report to .
[Apache Bloodhound] #619: Nested HTML forms in ticket view
#619: Nested HTML forms in ticket view -+- Reporter: olemis |Owner: Type: defect | Status: new Priority: major | Version: 0.6.0 Resolution: | -+- Lower level libraries implementing twill will raise an explicit ''SGML'' parser error when finding nested ''HTML'' forms ... like those in ticket view . The fact is that `//form[@id=addreply]` seems to be embedded inside `//form[@id=inplace-propertyform]` . When I view page source in ''Mozilla Firefox'' the former and the end tag of the later are highlighted in red. I see a few more tags highlighted in red too . -- Ticket URL: https://issues.apache.org/bloodhound/ticket/619 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound issue tracker
Re: [Apache Bloodhound] #619: Nested HTML forms in ticket view
#619: Nested HTML forms in ticket view +- Reporter: olemis | Owner: nobody Type: defect | Status: new Priority: blocker| Milestone: Release 7 Component: ui design |Version: 0.6.0 Resolution: | Keywords: ticket, starter +- Changes (by olemis): * component: = ui design * priority: major = blocker * owner: = nobody * milestone: = Release 7 * keywords: = ticket, starter Old description: Lower level libraries implementing twill will raise an explicit ''SGML'' parser error when finding nested ''HTML'' forms ... like those in ticket view . The fact is that `//form[@id=addreply]` seems to be embedded inside `//form[@id=inplace-propertyform]` . When I view page source in ''Mozilla Firefox'' the former and the end tag of the later are highlighted in red. I see a few more tags highlighted in red too . New description: Lower level libraries implementing twill will raise an explicit ''SGML'' parser error when finding nested ''HTML'' forms ... like those in ticket view . The fact is that `//form[@id=addreply]` seems to be embedded inside `//form[@id=inplace-propertyform]` . When I view page source in ''Mozilla Firefox'' the former and the end tag of the later are highlighted in red. I see a few more tags highlighted in red too . See [http://goo.gl/jrJ4Vy this message] for further details . -- Comment: This ticket is actually blocking me to continue with #387 . -- Ticket URL: https://issues.apache.org/bloodhound/ticket/619#comment:1 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound issue tracker
