Re: [Apache Bloodhound] #479: Embeddable tickets / objects
#479: Embeddable tickets / objects --+ Reporter: jdreimann| Owner: nobody Type: enhancement | Status: new Priority: major| Milestone: Component: dashboard|Version: Resolution: | Keywords: gsoc --+ Description changed by jdreimann: Old description: Many big open source projects have issue trackers built on trac, the same technology Bloodhound is built on. We're hoping to make it easier for people to refer to objects like tickets, milestones, versions or whole products in a meaningful way. That could be done by providing the ability for users to refer to them as embeddable, interactive objects, like is done with [http://support.google.com/youtube/bin/answer.py?hl=en-GBanswer=171780 youtube videos] and [https://dev.twitter.com/docs/embedded-tweets tweets]. New description: Many big open source projects have issue trackers built on trac, the same technology Bloodhound is built on. We're hoping to make it easier for people to refer to objects like tickets, milestones, versions or whole products in a meaningful way. That could be done by providing the ability for users to refer to them as embeddable, interactive objects, like is done with [http://www.kickstarter.com/projects/doublefine/double-fine- adventure/widget Kickstarter widgets], [http://support.google.com/youtube/bin/answer.py?hl=en-GBanswer=171780 youtube videos] and [https://dev.twitter.com/docs/embedded-tweets tweets]. -- -- Ticket URL: https://issues.apache.org/bloodhound/ticket/479#comment:2 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #481: Live syntax highlighting
#481: Live syntax highlighting --+ Reporter: jdreimann| Owner: nobody Type: enhancement | Status: new Priority: major| Milestone: Component: dashboard|Version: Resolution: | Keywords: gsoc --+ Comment (by jdreimann): [https://issues.apache.org/jira/browse/COMDEV-92 Related GSoC submission] in the COMDEV Jira project. -- Ticket URL: https://issues.apache.org/bloodhound/ticket/481#comment:1 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
[Apache Bloodhound] Batch modify: #152, #478, #479, #480, #481, #483, #486
Batch modification to #152, #478, #479, #480, #481, #483, #486 by jdreimann: keywords to gsoc2013submitted Comment: Tagging submitted tasks -- Tickets URL: https://issues.apache.org/bloodhound/query?id=152%2C478%2C479%2C480%2C481%2C483%2C486 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #488: Add Solr support to Bloodhound Search plugin
#488: Add Solr support to Bloodhound Search plugin + Reporter: andrej | Owner: nobody Type: defect | Status: new Priority: major | Milestone: Component: dashboard |Version: Resolution: | Keywords: gsoc + Changes (by andrej): * owner: = nobody * keywords: = gsoc * component: = dashboard Old description: New description: Bloodhound Search plugin architecture supports different search backends. Current plugin implementation supports Whoosh search backend. Apache Solr can be used as alternative search backend for Bloodhound Search when requirements are reliability, scalability and fault tolerance. -- -- Ticket URL: https://issues.apache.org/bloodhound/ticket/488#comment:1 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #488: Add Solr support to Bloodhound Search plugin
#488: Add Solr support to Bloodhound Search plugin + Reporter: andrej | Owner: nobody Type: defect | Status: new Priority: major | Milestone: Component: dashboard |Version: Resolution: | Keywords: gsoc + Comment (by jdreimann): [https://issues.apache.org/jira/browse/COMDEV-93 Relevant GSoC submission] in the COMDEV Jira project. -- Ticket URL: https://issues.apache.org/bloodhound/ticket/488#comment:2 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
[Apache Bloodhound] #489: Time series reports
#489: Time series reports -+ Reporter: jdreimann| Owner: nobody Type: enhancement | Status: new Priority: major| Milestone: Component: dashboard|Version: Keywords: gsoc | -+ In many organisations reports are tracking changes over time or and/or are prepared in a regular interval to capture information at a fixed point in time. Our reports functionality doesn't serve these cases very well at the moment. Users also can't query information as it was at a given date. One proposed solution to this to enhance reports to be scheduled and represent data in relation to time in better ways, as well as changes over time. -- Ticket URL: https://issues.apache.org/bloodhound/ticket/489 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #489: Time series reports
#489: Time series reports --+ Reporter: jdreimann| Owner: nobody Type: enhancement | Status: new Priority: major| Milestone: Component: dashboard|Version: Resolution: | Keywords: gsoc --+ Comment (by jdreimann): [https://issues.apache.org/jira/browse/COMDEV-94 Related GSoC submission] in the COMDEV Jira project. -- Ticket URL: https://issues.apache.org/bloodhound/ticket/489#comment:1 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #489: Time series reports
#489: Time series reports --+- Reporter: jdreimann| Owner: nobody Type: enhancement | Status: new Priority: major| Milestone: Component: dashboard|Version: Resolution: | Keywords: gsoc, gsoc2013submitted --+- Changes (by jdreimann): * keywords: gsoc = gsoc, gsoc2013submitted -- Ticket URL: https://issues.apache.org/bloodhound/ticket/489#comment:2 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #488: Add Solr support to Bloodhound Search plugin
#488: Add Solr support to Bloodhound Search plugin +- Reporter: andrej | Owner: nobody Type: defect | Status: new Priority: major | Milestone: Component: dashboard |Version: Resolution: | Keywords: gsoc, gsoc2013submitted +- Changes (by jdreimann): * keywords: gsoc = gsoc, gsoc2013submitted -- Ticket URL: https://issues.apache.org/bloodhound/ticket/488#comment:3 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #485: Topic-based pub/sub for IResourceChangeListener
#485: Topic-based pub/sub for IResourceChangeListener -+- Reporter: olemis | Owner: nobody Type: | Status: new enhancement| Milestone: Priority: major |Version: Component: trac core | Keywords: gsoc gsoc2013submitted Resolution: | IResourceChangeListener performance -+- Changes (by jdreimann): * keywords: gsoc IResourceChangeListener performance = gsoc gsoc2013submitted IResourceChangeListener performance Old description: Resource listeners often will watch events for a limited , well-known set of resource realms (e.g. `ticket` + `attachment` ) . The current dispatching strategy (i.e. `match_resource`) is mostly [http://en.wikipedia.org/wiki/Publish–subscribe_pattern#Message_filtering content based] . It behaves in `O(r * l)` order of magnitude . This might lead to a lot of extra (unnecessary) overhead . A performance improvement could be to allow listeners to register to dedicated realm channels (i.e. [http://en.wikipedia.org/wiki/Publish–subscribe_pattern#Message_filtering topic-based filtering]) , thus turning the dispatch algorithm into `O(l)` , at least when it is a ok to do so ;) PS: We shall not loose the current content-based filtering capabilities , so in advance I advocated using a hybrid strategy . New description: Resource listeners often will watch events for a limited, well-known set of resource realms (e.g. `ticket` + `attachment` ). The current dispatching strategy (i.e. `match_resource`) is mostly [http://en.wikipedia.org/wiki/Publish–subscribe_pattern#Message_filtering content based]. It behaves in `O(r * l)` order of magnitude. This might lead to a lot of extra (unnecessary) overhead. A performance improvement could be to allow listeners to register to dedicated realm channels (i.e. [http://en.wikipedia.org/wiki/Publish–subscribe_pattern#Message_filtering topic-based filtering]), thus turning the dispatch algorithm into `O(l)` , at least when it is a ok to do so ;) PS: We shall not loose the current content-based filtering capabilities , so in advance I advocated using a hybrid strategy. -- Comment: [https://issues.apache.org/jira/browse/COMDEV-95 Relevant GSoC submission] in COMDEV Jira project. -- Ticket URL: https://issues.apache.org/bloodhound/ticket/485#comment:2 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #489: Time series reports
#489: Time series reports --+- Reporter: jdreimann| Owner: nobody Type: enhancement | Status: new Priority: major| Milestone: Component: dashboard|Version: Resolution: | Keywords: gsoc, gsoc2013submitted --+- Comment (by olemis): jftr . somebody in my team is currently working on something related to this . -- Ticket URL: https://issues.apache.org/bloodhound/ticket/489#comment:3 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #489: Time series reports
#489: Time series reports --+- Reporter: jdreimann| Owner: nobody Type: enhancement | Status: new Priority: major| Milestone: Component: dashboard|Version: Resolution: | Keywords: gsoc, gsoc2013submitted --+- Comment (by rjollos): I think this would be a good feature. For reference, the only plugin I know of on trac-hacks that relates to solving this problem is the [th:SnapshotPlugin]. -- Ticket URL: https://issues.apache.org/bloodhound/ticket/489#comment:4 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
[Apache Bloodhound] New user registration: miron
New user registration for user miron -- Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #486: Abstract filesystem APIs
#486: Abstract filesystem APIs -+- Reporter: olemis | Owner: nobody Type: | Status: new enhancement| Milestone: Priority: minor |Version: Component: trac core | Keywords: filesystem attachment hdfs skydrive Resolution: | googledrive gsoc -+- Description changed by brane: Old description: The goal is to run instances of Bloodhound able to store some files (e.g. attachments) in other locations besides the file system . Initial targets might be [https://drive.google.com Google Drive] , [https://skydrive.live.com SkyDrive] or [http://hadoop.apache.org/docs/r1.0.4/hdfs_design.html HDFS] [http://hadoop.apache.org/docs/stable/hdfs_user_guide.html (1)] New description: The goal is to run instances of Bloodhound able to store some files (e.g. attachments) in other locations besides the file system . Initial targets might be [http://aws.amazon.com/s3/ Amazon S3], [https://drive.google.com Google Drive] , [https://skydrive.live.com SkyDrive] or [http://hadoop.apache.org/docs/r1.0.4/hdfs_design.html HDFS] [http://hadoop.apache.org/docs/stable/hdfs_user_guide.html (1)] -- -- Ticket URL: https://issues.apache.org/bloodhound/ticket/486#comment:4 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #486: Abstract filesystem APIs
#486: Abstract filesystem APIs -+- Reporter: olemis | Owner: nobody Type: | Status: new enhancement| Milestone: Priority: minor |Version: Component: trac core | Keywords: filesystem attachment hdfs skydrive Resolution: | googledrive gsoc -+- Description changed by brane: Old description: The goal is to run instances of Bloodhound able to store some files (e.g. attachments) in other locations besides the file system . Initial targets might be [http://aws.amazon.com/s3/ Amazon S3], [https://drive.google.com Google Drive] , [https://skydrive.live.com SkyDrive] or [http://hadoop.apache.org/docs/r1.0.4/hdfs_design.html HDFS] [http://hadoop.apache.org/docs/stable/hdfs_user_guide.html (1)] New description: The goal is to run instances of Bloodhound able to store some files (e.g. attachments) in other locations besides the local file system . Initial targets might be [http://aws.amazon.com/s3/ Amazon S3], [https://drive.google.com Google Drive] , [https://skydrive.live.com SkyDrive] or [http://hadoop.apache.org/docs/r1.0.4/hdfs_design.html HDFS] [http://hadoop.apache.org/docs/stable/hdfs_user_guide.html (1)] -- -- Ticket URL: https://issues.apache.org/bloodhound/ticket/486#comment:5 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #430: Multiproduct UI: Administration pages
#430: Multiproduct UI: Administration pages ---+ Reporter: matevzb | Owner: jure Type: defect| Status: new Priority: major | Milestone: Release 6 Component: multiproduct |Version: Resolution:| Keywords: product admin bep-0003 ---+ Changes (by jure): * status: closed = new * resolution: fixed = -- Ticket URL: https://issues.apache.org/bloodhound/ticket/430#comment:10 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #486: Abstract filesystem APIs
#486: Abstract filesystem APIs -+- Reporter: olemis | Owner: nobody Type: | Status: new enhancement| Milestone: Priority: minor |Version: Component: trac core | Keywords: filesystem attachment hdfs skydrive Resolution: | googledrive gsoc -+- Comment (by brane): Related submission in the [https://issues.apache.org/jira/browse/COMDEV-89 COMDEV Jira project] -- Ticket URL: https://issues.apache.org/bloodhound/ticket/486#comment:6 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #185: Typeahead for usernames on 'assign to' fields
#185: Typeahead for usernames on 'assign to' fields --+ Reporter: jdreimann| Owner: nobody Type: enhancement | Status: new Priority: minor| Milestone: Component: ui design|Version: Resolution: | Keywords: gsoc --+ Comment (by jdreimann): Replying to [comment:3 olemis]: I've removed the GSoC tag because a solution to this already exists (see gjm's coment). -- Ticket URL: https://issues.apache.org/bloodhound/ticket/185#comment:4 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #233: Autocomplete keywords
#233: Autocomplete keywords --+ Reporter: jdreimann| Owner: nobody Type: enhancement | Status: new Priority: minor| Milestone: Component: plugins |Version: Resolution: | Keywords: --+ Changes (by jdreimann): * keywords: gsoc = Old description: I would be very useful if we could autocomplete keywords, in order to stop users creating multiples with similar spelling etc. There's already a [http://trac-hacks.org/wiki/KeywordSuggestPlugin Trac- Hack] for this purpose. New description: I would be very useful if we could autocomplete keywords, in order to stop users creating multiples with similar spelling etc. There's already a [http://trac-hacks.org/wiki/KeywordSuggestPlugin Trac- Hack] for this purpose. Likely also related to #185, which asks to implement typeahead functionality for usernames. -- Comment: I'm removing the GSoC tag because this seems too small a task and a solution already exists for it, even if it isn't quite what we may like to see. -- Ticket URL: https://issues.apache.org/bloodhound/ticket/233#comment:3 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #151: Users should be able to watch objects
#151: Users should be able to watch objects --+ Reporter: jdreimann| Owner: nobody Type: enhancement | Status: new Priority: major| Milestone: Component: dashboard|Version: Resolution: | Keywords: --+ Changes (by jdreimann): * keywords: gsoc = Comment: I'm removing the GSoC tag because this issue seems to small for a 6-8 week project. The bigger issue of notifications is probably more relevant. -- Ticket URL: https://issues.apache.org/bloodhound/ticket/151#comment:4 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #16: Add functionality equivalent to 'ticket status by' progress bars into Milestone
#16: Add functionality equivalent to 'ticket status by' progress bars into Milestone --+- Reporter: gjm | Owner: Type: enhancement | Status: new Priority: trivial | Milestone: Unscheduled Component: dashboard|Version: Resolution: | Keywords: --+- Changes (by jdreimann): * priority: major = trivial * keywords: gsoc = Comment: I've removed the GSoC tag from this because it seems too trivial and small for a 6-8 week project. I will raise a task relating to showing a Roadmap instead which is a bigger, related tool that's probably still manageable given the time frame. -- Ticket URL: https://issues.apache.org/bloodhound/ticket/16#comment:8 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
[Apache Bloodhound] WikiStart modified
Page WikiStart was changed by jdreimann
Diff URL:
https://issues.apache.org/bloodhound/wiki/WikiStart?action=diffversion=21
Revision 21
Comment: Removed the (incubating) status from the header as the project has now
graduated.
Changes:
---8--8--8--8--8--8--8--8
Index: WikiStart
=
--- WikiStart (version: 20)
+++ WikiStart (version: 21)
@@ -1,4 +1,4 @@
-= Apache Bloodhound ^(incubating)^ =
+= Apache Bloodhound =
A tool created for issue tracking and managing of software projects.
{{{
#!html
---8--8--8--8--8--8--8--8
--
Page URL: https://issues.apache.org/bloodhound/wiki/WikiStart
Apache Bloodhound https://issues.apache.org/bloodhound/
The Apache Bloodhound (incubating) issue tracker
This is an automated message. Someone added your email address to be
notified of changes on 'WikiStart' page.
If it was not you, please report to .
Re: [Apache Bloodhound] #152: Make discovering WikiMacros easier
#152: Make discovering WikiMacros easier --+ Reporter: jdreimann| Owner: nobody Type: enhancement | Status: new Priority: major| Milestone: Component: dashboard|Version: Resolution: | Keywords: gsoc --+ Comment (by jdreimann): Related submission in the [https://issues.apache.org/jira/browse/COMDEV-90 COMDEV Jira project] -- Ticket URL: https://issues.apache.org/bloodhound/ticket/152#comment:2 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #185: Typeahead for usernames on 'assign to' fields
#185: Typeahead for usernames on 'assign to' fields --+- Reporter: jdreimann| Owner: nobody Type: enhancement | Status: new Priority: minor| Milestone: Component: ui design|Version: Resolution: | Keywords: starter --+- Changes (by rjollos): * keywords: gsoc = starter Comment: It has been discussed on the mailing list that this ticket is suitable for a new contributor, and a place to start is taking a close look at the [th:AutocompleteUsersPlugin]. -- Ticket URL: https://issues.apache.org/bloodhound/ticket/185#comment:5 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #16: Add functionality equivalent to 'ticket status by' progress bars into Milestone
#16: Add functionality equivalent to 'ticket status by' progress bars into Milestone --+- Reporter: gjm | Owner: Type: enhancement | Status: new Priority: trivial | Milestone: Unscheduled Component: dashboard|Version: Resolution: | Keywords: starter --+- Changes (by rjollos): * keywords: = starter -- Ticket URL: https://issues.apache.org/bloodhound/ticket/16#comment:9 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #233: Autocomplete keywords
#233: Autocomplete keywords --+- Reporter: jdreimann| Owner: nobody Type: enhancement | Status: new Priority: minor| Milestone: Component: plugins |Version: Resolution: | Keywords: starter --+- Changes (by rjollos): * keywords: = starter -- Ticket URL: https://issues.apache.org/bloodhound/ticket/233#comment:4 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #469: Some batch modify unit test cases are failing
#469: Some batch modify unit test cases are failing +--- Reporter: rjollos| Owner: rjollos Type: defect | Status: closed Priority: blocker| Milestone: Release 6 Component: trac core |Version: 0.4.0 Resolution: fixed | Keywords: ITicketFieldProvider ticket batch +--- Changes (by rjollos): * status: review = closed * resolution: = fixed Comment: (In [1460843]) Fixes #469: Fix for failing `BatchModify` unit test cases. The `TicketSystem` implements the `ITicketFieldProvider` interface, and also calls a method of the `ITicketFieldProvider` interface to get a list containing the ticket fields. When the `api.TicketSystem` component is not enabled, the fields provided by that class won't be returned in the call `TicketSystem.get_ticket_fields`. The fields returned by `TicketSystem.get_select_fields` and `TicketSystem.get_radio_fields` are built-in ticket fields, which some cases expect to be returned through the call `TicketSystem.get_ticket_fields`. Thank to Olemis for the patch. -- Ticket URL: https://issues.apache.org/bloodhound/ticket/469#comment:3 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
[Apache Bloodhound] #487: Test case `test_rss_conversion` in Trac core is failing
#487: Test case `test_rss_conversion` in Trac core is failing
---+---
Reporter: rjollos| Owner: nobody
Type: defect | Status: new
Priority: minor | Milestone: Release 6
Component: trac core |Version:
Keywords: unittest |
---+---
Here is another test case that is failing at the latest revision
(r1457457) of the source. I'm fairly sure this test case was not failing
when I reported #469, but it was failing earlier today before the patch
for #469 was applied.
{{{
test_unicode_verifyrev
(tracopt.versioncontrol.git.tests.PyGIT.UnicodeNameTestCase) ... ok
Mock (trac.test)
Doctest: trac.test.Mock ... ok
==
FAIL: test_rss_conversion
(trac.ticket.tests.conversion.TicketConversionTestCase)
--
Traceback (most recent call last):
File /home/user/Workspace/bh469/trac/trac/ticket/tests/conversion.py,
line 93, in test_rss_conversion
(content.replace('\r', ''), mimetype, ext))
AssertionError: Tuples differ: ('?xml version=1.0?\nrss ... !=
('?xml version=1.0?\nrss ...
First differing element 0:
?xml version=1.0?
rss xmlns:dc=http://purl.org/dc/elements/1.1/; version=2.0
channel
titleMy Project: Ticket #1: Foo/title
linkhttp://example.org/trac.cgi/ticket/1/link
descriptionlt;pgt;
Bar
lt;/pgt;
/description
languageen-us/language
generatorTrac 1.0.1/generator
/channel
/rss
?xml version=1.0?
rss xmlns:dc=http://purl.org/dc/elements/1.1/; version=2.0
channel
titleMy Project: Ticket #1: Foo/title
linkhttp://example.org/trac.cgi/ticket/1/link
descriptionlt;pgt;
Bar
lt;/pgt;
/description
languageen-us/language
generatorTrac 1.0.1
/generator
/channel
/rss
Diff is 1444 characters long. Set self.maxDiff to None to see it.
--
Ran 1215 tests in 14.057s
FAILED (failures=1)
}}}
--
Ticket URL: https://issues.apache.org/bloodhound/ticket/487
Apache Bloodhound https://issues.apache.org/bloodhound/
The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #477: Add multi-product aware security to Bloodhound Search (was: Add multi-product aware security to Bloodhoun Search)
#477: Add multi-product aware security to Bloodhound Search -+- Reporter: andrej | Owner: nobody Type: defect | Status: new Priority: major | Milestone: Component: dashboard |Version: Resolution: | Keywords: bep-0004 bep-0004-stable | multiproduct -+- -- Ticket URL: https://issues.apache.org/bloodhound/ticket/477#comment:2 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #430: Multiproduct UI: Administration pages
#430: Multiproduct UI: Administration pages ---+ Reporter: matevzb | Owner: jure Type: defect| Status: closed Priority: major | Milestone: Release 6 Component: multiproduct |Version: Resolution: fixed | Keywords: product admin bep-0003 ---+ Changes (by jure): * status: assigned = closed * resolution: = fixed Comment: t430_r1457691_product_plugin_admin.diff applied in r1460318 t430_r1457691_product_admin_whitelist.diff applied with minor changes in r1460332, check `SudoPermissionContext.__call__` ... t430_r1458841_product_admin_defaults.diff applied in 1460335 -- Ticket URL: https://issues.apache.org/bloodhound/ticket/430#comment:9 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #475: Console admin commands (trac-admin) for products
#475: Console admin commands (trac-admin) for products -+- Reporter: olemis | Owner: olemis Type: task| Status: accepted Priority: major | Milestone: Release 6 Component: |Version: multiproduct | Keywords: bep-0003 multiproduct admin console Resolution: | TracAdmin -+- Comment (by jure): Replying to [comment:2 olemis]: [attachment:t475_r1457691_product_trac_admin.diff Attached patch] (built on top of patches submitted for #430) implements the following console admin commands : - product list - product admin It also supports autocompletion for product prefix and all levels supported by target sub-command provider . See [http://pastebin.com/BUHrtE1A this sample admin session] Looks great! Patch t475_r1457691_product_trac_admin.diff applied in r1460340 PS: Should I follow and implement these ones ? - product add - product chown - product remove - product rename IMO add, rename (namedescription change) and chown would be useful. It was discussed on the @dev that we might not actually support remove operation on products but rather go for archive or something similar. -- Ticket URL: https://issues.apache.org/bloodhound/ticket/475#comment:3 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #16: Add functionality equivalent to 'ticket status by' progress bars into Milestone
#16: Add functionality equivalent to 'ticket status by' progress bars into Milestone --+- Reporter: gjm | Owner: Type: enhancement | Status: new Priority: major| Milestone: Unscheduled Component: dashboard|Version: Resolution: | Keywords: gsoc --+- Changes (by brane): * status: assigned = new -- Ticket URL: https://issues.apache.org/bloodhound/ticket/16#comment:7 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #480: Twitter card integration (and other social tags)
#480: Twitter card integration (and other social tags) --+ Reporter: jdreimann| Owner: nobody Type: enhancement | Status: new Priority: major| Milestone: Component: dashboard|Version: Resolution: | Keywords: gsoc --+ Comment (by brane): Related submission in the [https://issues.apache.org/jira/browse/COMDEV-85 COMDEV Jira project] -- Ticket URL: https://issues.apache.org/bloodhound/ticket/480#comment:2 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #483: Improved support for remote svn repository browser
#483: Improved support for remote svn repository browser --+- Reporter: olemis | Owner: nobody Type: enhancement | Status: new Priority: major| Milestone: Component: plugins |Version: Resolution: | Keywords: gsoc versioncontrol svn --+- Changes (by brane): * type: task = enhancement Comment: Not a duplicate of #83 IMO, but definitely related. Also related to #478. -- Ticket URL: https://issues.apache.org/bloodhound/ticket/483#comment:4 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #483: Improved support for remote svn repository browser
#483: Improved support for remote svn repository browser --+- Reporter: olemis | Owner: nobody Type: enhancement | Status: new Priority: major| Milestone: Component: plugins |Version: Resolution: | Keywords: gsoc versioncontrol svn --+- Comment (by brane): Related submission in the [https://issues.apache.org/jira/browse/COMDEV-86 COMDEV Jira project] -- Ticket URL: https://issues.apache.org/bloodhound/ticket/483#comment:5 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #89: remote svn repository support
#89: remote svn repository support --+ Reporter: gjm | Owner: nobody Type: enhancement | Status: new Priority: major| Milestone: Unscheduled Component: siteadmin|Version: Resolution: | Keywords: versioncontrol svn --+ Comment (by brane): Related submission in the [https://issues.apache.org/jira/browse/COMDEV-86 COMDEV Jira project] -- Ticket URL: https://issues.apache.org/bloodhound/ticket/89#comment:4 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #482: Expose TODOs from the code base in the UI
#482: Expose TODOs from the code base in the UI --+ Reporter: jdreimann| Owner: nobody Type: enhancement | Status: new Priority: major| Milestone: Component: dashboard|Version: Resolution: | Keywords: gsoc --+ Comment (by andrej): Bloodhound Search plugin with additional source indexing can be potentially used for this purpose. -- Ticket URL: https://issues.apache.org/bloodhound/ticket/482#comment:1 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
[Apache Bloodhound] #486: Abstract filesystem APIs
#486: Abstract filesystem APIs --+--- Reporter: olemis |Owner: Type: enhancement | Status: new Priority: major| Version: Resolution: | --+--- The goal is to run instances of Bloodhound able to store some files (e.g. attachments) in other locations besides the file system . Initial targets might be [https://drive.google.com] , [https://skydrive.live.com SkyDrive] or [http://hadoop.apache.org/docs/r1.0.4/hdfs_design.html HDFS] [http://hadoop.apache.org/docs/stable/hdfs_user_guide.html (1)] -- Ticket URL: https://issues.apache.org/bloodhound/ticket/486 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #486: Abstract filesystem APIs
#486: Abstract filesystem APIs -+- Reporter: olemis | Owner: nobody Type: | Status: new enhancement| Milestone: Priority: major |Version: Component: trac core | Keywords: filesystem attachments hdfs Resolution: | skydrive googledrive gsoc -+- Changes (by olemis): * keywords: = filesystem attachments hdfs skydrive googledrive gsoc * owner: = nobody * component: = trac core -- Ticket URL: https://issues.apache.org/bloodhound/ticket/486#comment:1 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #486: Abstract filesystem APIs
#486: Abstract filesystem APIs -+- Reporter: olemis | Owner: nobody Type: | Status: new enhancement| Milestone: Priority: major |Version: Component: trac core | Keywords: filesystem attachments hdfs Resolution: | skydrive googledrive gsoc -+- Description changed by olemis: Old description: The goal is to run instances of Bloodhound able to store some files (e.g. attachments) in other locations besides the file system . Initial targets might be [https://drive.google.com] , [https://skydrive.live.com SkyDrive] or [http://hadoop.apache.org/docs/r1.0.4/hdfs_design.html HDFS] [http://hadoop.apache.org/docs/stable/hdfs_user_guide.html (1)] New description: The goal is to run instances of Bloodhound able to store some files (e.g. attachments) in other locations besides the file system . Initial targets might be [https://drive.google.com Google Drive] , [https://skydrive.live.com SkyDrive] or [http://hadoop.apache.org/docs/r1.0.4/hdfs_design.html HDFS] [http://hadoop.apache.org/docs/stable/hdfs_user_guide.html (1)] -- -- Ticket URL: https://issues.apache.org/bloodhound/ticket/486#comment:2 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #486: Abstract filesystem APIs
#486: Abstract filesystem APIs -+- Reporter: olemis | Owner: nobody Type: | Status: new enhancement| Milestone: Priority: minor |Version: Component: trac core | Keywords: filesystem attachment hdfs skydrive Resolution: | googledrive gsoc -+- Changes (by olemis): * priority: major = minor * keywords: filesystem attachments hdfs skydrive googledrive gsoc = filesystem attachment hdfs skydrive googledrive gsoc -- Ticket URL: https://issues.apache.org/bloodhound/ticket/486#comment:3 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
[Apache Bloodhound] New user registration: otto
New user registration for user otto -- Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #482: Expose TODOs from the code base in the UI
#482: Expose TODOs from the code base in the UI --+ Reporter: jdreimann| Owner: nobody Type: enhancement | Status: new Priority: major| Milestone: Component: dashboard|Version: Resolution: | Keywords: gsoc --+ Comment (by rjollos): I mention just for reference, that a similar feature has been implemented in the [th:CodeTagsPlugin]. -- Ticket URL: https://issues.apache.org/bloodhound/ticket/482#comment:2 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #476: Integrate bhsearch into multi-product environment
#476: Integrate bhsearch into multi-product environment -+- Reporter: andrej | Owner: nobody Type: | Status: new enhancement| Milestone: Release 6 Priority: major |Version: Component: search | Keywords: bep-0004 bep-0004-stable multi- Resolution: | product -+- Changes (by andrej): * keywords: = bep-0004 bep-0004-stable multi-product * owner: = nobody * component: = search * milestone: = Release 6 Old description: New description: Bloodhoun Search plugin must be integrated into multi-product environment with the following changes: * /product/xxx/bhsearch url should be redirected to global url .../bhsearch?...product=xxx * add product field to bhsearch index and set product for specific document * re-index should index documents from all product -- -- Ticket URL: https://issues.apache.org/bloodhound/ticket/476#comment:1 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
[Apache Bloodhound] #477: Add multi-product aware security to Bloodhoun Search
#477: Add multi-product aware security to Bloodhoun Search -+--- Reporter: andrej |Owner: Type: defect | Status: new Priority: major | Version: Resolution: | -+--- -- Ticket URL: https://issues.apache.org/bloodhound/ticket/477 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
[Apache Bloodhound] #478: SVN pubsub integration
#478: SVN pubsub integration ---+ Reporter: jdreimann | Owner: nobody Type: defect | Status: new Priority: major | Milestone: Component: dashboard |Version: Keywords: gsoc | ---+ SVN 1.8 will introduce a publish-subscribe system called svnpubsub. Integrating this into Bloodhound could be used for many good purposes, one being the support for remote repos. This has been recognised as an issue by trac for 9 years, but never been solved yet: http://trac.edgewall.org/ticket/493 -- Ticket URL: https://issues.apache.org/bloodhound/ticket/478 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
[Apache Bloodhound] #480: Twitter card integration (and other social tags)
#480: Twitter card integration (and other social tags) ---+ Reporter: jdreimann | Owner: nobody Type: defect | Status: new Priority: major | Milestone: Component: dashboard |Version: Keywords: gsoc | ---+ Many big open source projects have issue trackers built on trac, the same technology Bloodhound is built on. We're hoping to make it easier for people to refer to objects like tickets, milestones, versions or whole products in a meaningful way. One approach to this is to provide [https://dev.twitter.com/docs/cards Twitter card integration] for a richer experience. In addition [http://davidwalsh.name/facebook-meta-tags Facebook Meta Tags] could be helpful. Google Plus [http://stackoverflow.com/a/8295748/1986861 relies on schema.org metatags], which we may also want to conform to. -- Ticket URL: https://issues.apache.org/bloodhound/ticket/480 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
[Apache Bloodhound] Batch modify: #478, #479, #480
Batch modification to #478, #479, #480 by jdreimann: type to enhancement -- Tickets URL: https://issues.apache.org/bloodhound/query?id=478%2C479%2C480 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #471: Merge activity feed + change history
#471: Merge activity feed + change history
--+--
Reporter: jdreimann| Owner: gjm
Type: enhancement | Status: accepted
Priority: major| Milestone: Release 6
Component: dashboard|Version:
Resolution: | Keywords: ui, comments, change history
--+--
Comment (by gjm):
r1459967 adds overrides the global behaviour of timeline events to make
sure that the activity widget has all ticket events available (adding
{{{'ticket_details'}}} to the list of available filters when the resource
is a ticket).
--
Ticket URL: https://issues.apache.org/bloodhound/ticket/471#comment:4
Apache Bloodhound https://issues.apache.org/bloodhound/
The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #475: Console admin commands (trac-admin) for products
#475: Console admin commands (trac-admin) for products
-+-
Reporter: olemis | Owner: olemis
Type: task| Status: accepted
Priority: major | Milestone: Release 6
Component: |Version:
multiproduct | Keywords: bep-0003 multiproduct admin console
Resolution: | TracAdmin
-+-
Comment (by olemis):
[attachment:t475_r1457691_product_trac_admin.diff Attached patch] (built
on top of patches submitted for #430) implements the following console
admin commands :
- product list
- product admin
It also supports autocompletion for product prefix and all levels
supported by target sub-command provider . See
[http://pastebin.com/BUHrtE1A this sample admin session]
Patch details
{{{
#!sh
$ hg qapplied
t430/t430_r1457691_product_plugin_admin.diff
t430/t430_r1457691_product_admin_whitelist.diff
t430/t430_r1458841_product_admin_defaults.diff
t475/t475_r1457691_product_trac_admin.diff
$ hg log -r qparent --template=[{svnrev}] - {desc}\n
[1459313] - #325 - Multiproduct UI: Dashboard (product well layout minor
fix)
}}}
PS: Should I follow and implement these ones ?
- product add
- product chown
- product remove
- product rename
--
Ticket URL: https://issues.apache.org/bloodhound/ticket/475#comment:2
Apache Bloodhound https://issues.apache.org/bloodhound/
The Apache Bloodhound (incubating) issue tracker
[Apache Bloodhound] #483: Improved support for remote svn repository browser
#483: Improved support for remote svn repository browser -+--- Reporter: olemis |Owner: Type: task| Status: new Priority: major | Version: Resolution: | -+--- Enhance [http://www.meadowy.org/~gotoh/hg/remote-svn-plugin/ remote svn plugin] to integrate it with Trac=1.x , multi-repository APIs and other features included since [http://www.meadowy.org/~gotoh/hg/remote-svn- plugin/index.cgi/rev/3fefbe9a3b1c last change] -- Ticket URL: https://issues.apache.org/bloodhound/ticket/483 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #484: Patch workflows tightly coupled to version control
#484: Patch workflows tightly coupled to version control -+- Reporter: olemis | Owner: nobody Type: | Status: new enhancement| Milestone: Priority: major |Version: Component: trac core | Keywords: patch ticket workflow Resolution: | versioncontrol svn mercurial mq gsoc -+- Changes (by olemis): * keywords: patch ticket workflow versioncontrol svn mercurial mq = patch ticket workflow versioncontrol svn mercurial mq gsoc -- Ticket URL: https://issues.apache.org/bloodhound/ticket/484#comment:2 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #483: Improved support for remote svn repository browser
#483: Improved support for remote svn repository browser --+- Reporter: olemis | Owner: nobody Type: task | Status: new Priority: major| Milestone: Component: plugins |Version: Resolution: | Keywords: gsoc versioncontrol svn --+- Comment (by olemis): related to #89 (duplicate ?) -- Ticket URL: https://issues.apache.org/bloodhound/ticket/483#comment:3 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #89: remote svn repository support
#89: remote svn repository support --+ Reporter: gjm | Owner: nobody Type: enhancement | Status: new Priority: major| Milestone: Unscheduled Component: siteadmin|Version: Resolution: | Keywords: versioncontrol svn --+ Changes (by olemis): * keywords: = versioncontrol svn -- Ticket URL: https://issues.apache.org/bloodhound/ticket/89#comment:3 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #16: Add functionality equivalent to 'ticket status by' progress bars into Milestone
#16: Add functionality equivalent to 'ticket status by' progress bars into Milestone --+- Reporter: gjm | Owner: Type: enhancement | Status: assigned Priority: major| Milestone: Unscheduled Component: dashboard|Version: Resolution: | Keywords: gsoc --+- Changes (by olemis): * keywords: = gsoc -- Ticket URL: https://issues.apache.org/bloodhound/ticket/16#comment:6 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #484: Patch workflows tightly coupled to version control
#484: Patch workflows tightly coupled to version control -+- Reporter: olemis | Owner: nobody Type: | Status: new enhancement| Milestone: Priority: major |Version: Component: trac core | Keywords: patch ticket workflow Resolution: | versioncontrol svn mercurial mq gsoc -+- Description changed by olemis: Old description: Implement a patch management system for Bloodhound (Trac) considering the following : - Integrate patch development , handling and commit into ticket workflow . - Automate actions like ticket updates on patch chaged Particularly focused on Apache™ Subversion and trac:wiki:TracMercurial , which already supports MQ extension New description: Implement a patch management system for Bloodhound (Trac) considering the following : - Integrate patch development , handling and commit into ticket workflow . - Automate actions like ticket updates on patch change / upload Particularly focused on Apache™ Subversion and trac:wiki:TracMercurial , which already supports MQ extension -- -- Ticket URL: https://issues.apache.org/bloodhound/ticket/484#comment:3 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #142: Product-specific permissions
#142: Product-specific permissions ---+- Reporter: olemis| Owner: nobody Type: task | Status: closed Priority: major | Milestone: Unscheduled Component: multiproduct |Version: Resolution: duplicate | Keywords: permissions web_ui multiproduct ---+- Changes (by olemis): * status: new = closed * resolution: = duplicate Comment: superseded by #438 , #288 , #355 and maybe [bep:0003#reference- implementation other multi-product tickets] -- Ticket URL: https://issues.apache.org/bloodhound/ticket/142#comment:2 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #152: Make discovering WikiMacros easier
#152: Make discovering WikiMacros easier --+ Reporter: jdreimann| Owner: nobody Type: enhancement | Status: new Priority: major| Milestone: Component: dashboard|Version: Resolution: | Keywords: gsoc --+ Changes (by olemis): * keywords: = gsoc * component: ui design = dashboard -- Ticket URL: https://issues.apache.org/bloodhound/ticket/152#comment:1 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #151: Users should be able to watch objects
#151: Users should be able to watch objects --+ Reporter: jdreimann| Owner: nobody Type: enhancement | Status: new Priority: major| Milestone: Component: dashboard|Version: Resolution: | Keywords: gsoc --+ Changes (by olemis): * keywords: = gsoc -- Ticket URL: https://issues.apache.org/bloodhound/ticket/151#comment:3 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #233: Autocomplete keywords
#233: Autocomplete keywords --+ Reporter: jdreimann| Owner: nobody Type: enhancement | Status: new Priority: minor| Milestone: Component: plugins |Version: Resolution: | Keywords: gsoc --+ Changes (by olemis): * keywords: = gsoc -- Ticket URL: https://issues.apache.org/bloodhound/ticket/233#comment:2 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #231: Batch create tickets from wiki lists
#231: Batch create tickets from wiki lists --+ Reporter: jdreimann| Owner: nobody Type: enhancement | Status: new Priority: trivial | Milestone: Component: ui design|Version: Resolution: | Keywords: gsoc --+ Changes (by olemis): * keywords: = gsoc -- Ticket URL: https://issues.apache.org/bloodhound/ticket/231#comment:6 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #170: CSS rules for links
#170: CSS rules for links --+- Reporter: olemis | Owner: jdreimann Type: enhancement | Status: review Priority: major| Milestone: Release 6 Component: ui design|Version: Resolution: | Keywords: css links bootstrap --+- Changes (by olemis): * milestone: = Release 6 Comment: I think there's a chance to take a look into this one . Maybe related to a [http://mail-archives.apache.org/mod_mbox/incubator-bloodhound- dev/201303.mbox/%3cCAPt9QwQSmXghCeY- 3qw4_oiy6tqy3voeo3prmtds8ud103w...@mail.gmail.com%3e comment by @rjollos] . -- Ticket URL: https://issues.apache.org/bloodhound/ticket/170#comment:6 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #185: Typeahead for usernames on 'assign to' fields
#185: Typeahead for usernames on 'assign to' fields --+ Reporter: jdreimann| Owner: nobody Type: enhancement | Status: new Priority: minor| Milestone: Component: ui design|Version: Resolution: | Keywords: gsoc --+ Changes (by olemis): * keywords: = gsoc -- Ticket URL: https://issues.apache.org/bloodhound/ticket/185#comment:3 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
[Apache Bloodhound] #485: Topic-based pub/sub for IResourceChangeListener
#485: Topic-based pub/sub for IResourceChangeListener --+--- Reporter: olemis |Owner: Type: enhancement | Status: new Priority: major| Version: Resolution: | --+--- Resource listeners often will watch events for a limited , well-known set of resource realms (e.g. `ticket` + `attachment` ) . The current dispatching strategy (i.e. `match_resource`) is mostly [http://en.wikipedia.org/wiki/Publish–subscribe_pattern#Message_filtering content based] . It behaves in `O(r * l)` order of magnitude . This might lead to a lot of extra (unnecessary) overhead . A performance improvement could be to allow listeners to register to dedicated realm channels (i.e. [http://en.wikipedia.org/wiki/Publish–subscribe_pattern#Message_filtering topic-based filtering]) , thus turning the dispatch algorithm into `O(l)` . PS: We shall not loose the current content-based filtering capabilities , so in advance I advocated using a hybrid strategy . -- Ticket URL: https://issues.apache.org/bloodhound/ticket/485 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #485: Topic-based pub/sub for IResourceChangeListener
#485: Topic-based pub/sub for IResourceChangeListener -+- Reporter: olemis | Owner: nobody Type: | Status: new enhancement| Milestone: Priority: major |Version: Component: trac core | Keywords: gsoc IResourceChangeListener Resolution: | performance -+- Changes (by olemis): * owner: = nobody * keywords: = gsoc IResourceChangeListener performance * component: = trac core Old description: Resource listeners often will watch events for a limited , well-known set of resource realms (e.g. `ticket` + `attachment` ) . The current dispatching strategy (i.e. `match_resource`) is mostly [http://en.wikipedia.org/wiki/Publish–subscribe_pattern#Message_filtering content based] . It behaves in `O(r * l)` order of magnitude . This might lead to a lot of extra (unnecessary) overhead . A performance improvement could be to allow listeners to register to dedicated realm channels (i.e. [http://en.wikipedia.org/wiki/Publish–subscribe_pattern#Message_filtering topic-based filtering]) , thus turning the dispatch algorithm into `O(l)` . PS: We shall not loose the current content-based filtering capabilities , so in advance I advocated using a hybrid strategy . New description: Resource listeners often will watch events for a limited , well-known set of resource realms (e.g. `ticket` + `attachment` ) . The current dispatching strategy (i.e. `match_resource`) is mostly [http://en.wikipedia.org/wiki/Publish–subscribe_pattern#Message_filtering content based] . It behaves in `O(r * l)` order of magnitude . This might lead to a lot of extra (unnecessary) overhead . A performance improvement could be to allow listeners to register to dedicated realm channels (i.e. [http://en.wikipedia.org/wiki/Publish–subscribe_pattern#Message_filtering topic-based filtering]) , thus turning the dispatch algorithm into `O(l)` , at least when it is a ok to do so ;) PS: We shall not loose the current content-based filtering capabilities , so in advance I advocated using a hybrid strategy . -- -- Ticket URL: https://issues.apache.org/bloodhound/ticket/485#comment:1 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #430: Multiproduct UI: Administration pages
panel without meta-perm in product env ... ok Plugin admin panel without meta-perm in product env ... ok -- Ran 23 tests in 2.220s OK }}} -- Ticket URL: https://issues.apache.org/bloodhound/ticket/430#comment:7 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #430: Multiproduct UI: Administration pages
#430: Multiproduct UI: Administration pages ---+ Reporter: matevzb | Owner: jure Type: defect| Status: assigned Priority: major | Milestone: Release 6 Component: multiproduct |Version: Resolution:| Keywords: product admin bep-0003 ---+ Changes (by olemis): * owner: matevzb = jure * status: new = assigned -- Ticket URL: https://issues.apache.org/bloodhound/ticket/430#comment:8 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #325: Multiproduct UI: Dashboard
#325: Multiproduct UI: Dashboard --+--- Reporter: peter| Owner: matevzb Type: enhancement | Status: assigned Priority: major| Milestone: Release 6 Component: dashboard|Version: Resolution: | Keywords: --+--- Comment (by matevzb): Added versions and components in r1459300. -- Ticket URL: https://issues.apache.org/bloodhound/ticket/325#comment:9 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #472: Compatibility with trac search
#472: Compatibility with trac search --+ Reporter: astaric | Owner: nobody Type: enhancement | Status: closed Priority: major| Milestone: Component: search |Version: Resolution: fixed| Keywords: bep-0004 bep-0004-beta --+ Changes (by andrej): * status: new = closed * resolution: = fixed -- Ticket URL: https://issues.apache.org/bloodhound/ticket/472#comment:2 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #450: TracLinks for BloodhoundSeach plugin - after #390
#450: TracLinks for BloodhoundSeach plugin - after #390 -+- Reporter: olemis | Owner: nobody Type: task| Status: new Priority: major | Milestone: Component: search |Version: Resolution: | Keywords: search TracLinks bep-0004 | bep-0004-stable -+- Changes (by andrej): * keywords: search TracLinks bep-0004 bep-0004-beta = search TracLinks bep-0004 bep-0004-stable -- Ticket URL: https://issues.apache.org/bloodhound/ticket/450#comment:4 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #391: Add security support to Bloodhound Search
#391: Add security support to Bloodhound Search --+-- Reporter: andrej | Owner: nobody Type: enhancement | Status: new Priority: major| Milestone: Release 6 Component: search |Version: 0.4.0 Resolution: | Keywords: bep-0004 bep-0004-stable --+-- Changes (by andrej): * keywords: bep-0004 bep-0004-beta = bep-0004 bep-0004-stable Old description: Add search filter to query based user security context New description: Add search filter to query based user security context in multi-product environment. -- -- Ticket URL: https://issues.apache.org/bloodhound/ticket/391#comment:2 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #316: UI mockup for improved search prototype
#316: UI mockup for improved search prototype --+- Reporter: andrej | Owner: nobody Type: enhancement | Status: new Priority: major| Milestone: Component: search |Version: Resolution: | Keywords: search bep-0004 bep-0004-stable --+- Changes (by andrej): * keywords: search bep-0004 bep-0004-beta = search bep-0004 bep-0004-stable Old description: As proposed in [wiki:Proposals/BEP-0004 BEP-0004] and discussed on mailing list, improved search plugin needs updated UI mockup. There were also discusion to move query builder (and filters?) on the right side. Please consider below initial proposal that is far from final version: [[Image(mockup_all_resources_prototype.png)]] New description: As proposed in [wiki:Proposals/BEP-0004 BEP-0004] and discussed on mailing list, improved search plugin needs updated UI mockup. There were also discusion to move query builder (and filters?) on the right side. Mockups are attached to [wiki:Proposals/BEP-0004 BEP-0004] page and are discussed on dev mailing list. -- -- Ticket URL: https://issues.apache.org/bloodhound/ticket/316#comment:6 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
[Apache Bloodhound] #474: responsive layout broken
#474: responsive layout broken ---+--- Reporter: matevzb| Owner: nobody Type: defect | Status: new Priority: major | Milestone: Release 6 Component: ui design |Version: Keywords: | ---+--- There are a couple of issues with responsive layout in the last builds: * The title and the navbar are incorrectly aligned at smaller resolutions (image1) * The sticky nav overflows at smaller resolutions (see image2) * The ticket area becomes horizontally scrollable at specific resolutions, as the body overflows (image3) - note that this may be OS X-specific, when Show scrollbars is set to When scrolling in Preferences/General -- Ticket URL: https://issues.apache.org/bloodhound/ticket/474 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #316: UI mockup for improved search prototype
#316: UI mockup for improved search prototype --+- Reporter: andrej | Owner: jdreimann Type: enhancement | Status: assigned Priority: major| Milestone: Component: search |Version: Resolution: | Keywords: search bep-0004 bep-0004-stable --+- Changes (by jdreimann): * owner: nobody = jdreimann * status: new = assigned -- Ticket URL: https://issues.apache.org/bloodhound/ticket/316#comment:7 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #471: Merge activity feed + change history
#471: Merge activity feed + change history --+-- Reporter: jdreimann| Owner: gjm Type: enhancement | Status: accepted Priority: major| Milestone: Release 6 Component: dashboard|Version: Resolution: | Keywords: ui, comments, change history --+-- Changes (by gjm): * owner: nobody = gjm * status: new = accepted * milestone: = Release 6 Comment: I haven't noted any particular worries about this on bh-dev so I'll accept and try to work towards making this possible -- Ticket URL: https://issues.apache.org/bloodhound/ticket/471#comment:2 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #471: Merge activity feed + change history
#471: Merge activity feed + change history --+-- Reporter: jdreimann| Owner: gjm Type: enhancement | Status: accepted Priority: major| Milestone: Release 6 Component: dashboard|Version: Resolution: | Keywords: ui, comments, change history --+-- Comment (by gjm): r1459423 makes the activity widget for tickets show the full history of activity -- Ticket URL: https://issues.apache.org/bloodhound/ticket/471#comment:3 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #316: UI mockup for improved search prototype
#316: UI mockup for improved search prototype --+- Reporter: andrej | Owner: jdreimann Type: enhancement | Status: assigned Priority: major| Milestone: Component: search |Version: Resolution: | Keywords: search bep-0004 bep-0004-stable --+- Description changed by jdreimann: Old description: As proposed in [wiki:Proposals/BEP-0004 BEP-0004] and discussed on mailing list, improved search plugin needs updated UI mockup. There were also discusion to move query builder (and filters?) on the right side. Mockups are attached to [wiki:Proposals/BEP-0004 BEP-0004] page and are discussed on dev mailing list. New description: As proposed in [wiki:Proposals/BEP-0004 BEP-0004] and discussed on mailing list, improved search plugin needs updated UI mockup. There were also discusion to move query builder (and filters?) on the right side. Mockups are attached to [wiki:Proposals/BEP-0004 BEP-0004] page and are [http://markmail.org/thread/hcisr3pxbxiggxqf discussed on dev mailing list]. This is [https://issues.apache.org/bloodhound/attachment/wiki/Proposals/BEP-0004/search.png the latest mockup]. -- -- Ticket URL: https://issues.apache.org/bloodhound/ticket/316#comment:8 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
[Apache Bloodhound] #475: Console admin commands (trac-admin) for products
#475: Console admin commands (trac-admin) for products -+--- Reporter: olemis |Owner: Type: task| Status: new Priority: major | Version: Resolution: | -+--- Includes CRUD ops for products and the whole set of commands for product environments. -- Ticket URL: https://issues.apache.org/bloodhound/ticket/475 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #475: Console admin commands (trac-admin) for products
#475: Console admin commands (trac-admin) for products -+- Reporter: olemis | Owner: olemis Type: task| Status: accepted Priority: major | Milestone: Release 6 Component: |Version: multiproduct | Keywords: bep-0003 multiproduct admin console Resolution: | TracAdmin -+- Changes (by olemis): * status: new = accepted * keywords: = bep-0003 multiproduct admin console TracAdmin * component: = multiproduct * owner: = olemis * milestone: = Release 6 -- Ticket URL: https://issues.apache.org/bloodhound/ticket/475#comment:1 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #432: PermRedirectPlugin: TypeError: issubclass() arg 1 must be a class
#432: PermRedirectPlugin: TypeError: issubclass() arg 1 must be a class --+ Reporter: rjollos | Owner: rjollos Type: defect | Status: new Priority: major| Milestone: Component: plugins |Version: Resolution: | Keywords: PermRedirectPlugin --+ Comment (by rjollos): This seems to have been fixed with the upgrade to [th:PermRedirectPlugin] 3.0. -- Ticket URL: https://issues.apache.org/bloodhound/ticket/432#comment:3 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #432: PermRedirectPlugin: TypeError: issubclass() arg 1 must be a class
#432: PermRedirectPlugin: TypeError: issubclass() arg 1 must be a class --+ Reporter: rjollos | Owner: rjollos Type: defect | Status: closed Priority: major| Milestone: Component: plugins |Version: Resolution: fixed| Keywords: PermRedirectPlugin --+ Changes (by rjollos): * status: new = closed * resolution: = fixed -- Ticket URL: https://issues.apache.org/bloodhound/ticket/432#comment:4 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #460: Split submit and workflow on tickets
#460: Split submit and workflow on tickets --+--- Reporter: gjm | Owner: gjm Type: enhancement | Status: closed Priority: major| Milestone: Release 5 Component: dashboard|Version: 0.4.0 Resolution: fixed| Keywords: --+--- Changes (by gjm): * status: accepted = closed * resolution: = fixed * milestone: = Release 5 -- Ticket URL: https://issues.apache.org/bloodhound/ticket/460#comment:3 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #438: Implement and enforce product permission policy
#438: Implement and enforce product permission policy ---+-- Reporter: olemis| Owner: jure Type: task | Status: closed Priority: critical | Milestone: Release 6 Component: multiproduct |Version: Resolution: fixed | Keywords: permission security bep-0003 ---+-- Comment (by olemis): Replying to [comment:10 jure]: t438_r1457691_cpmngr_xtpt.diff applied in t1458170. scheduled for trac:milestone:1.0.2 (see trac:comment:6:ticket:11121 ) -- Ticket URL: https://issues.apache.org/bloodhound/ticket/438#comment:12 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #325: Multiproduct UI: Dashboard
#325: Multiproduct UI: Dashboard --+--- Reporter: peter| Owner: matevzb Type: enhancement | Status: assigned Priority: major| Milestone: Release 6 Component: dashboard|Version: Resolution: | Keywords: --+--- Comment (by matevzb): Moving towards UI mockup in r1459053, added Product wells for holding product specific info (milestones for now, versions and components will follow). -- Ticket URL: https://issues.apache.org/bloodhound/ticket/325#comment:8 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #457: Can't navigate to wiki page history
#457: Can't navigate to wiki page history +--- Reporter: rjollos| Owner: rjollos Type: defect | Status: closed Priority: major | Milestone: Release 6 Component: ui design |Version: Resolution: fixed | Keywords: +--- Comment (by rjollos): Patch has been submitted to Trac in trac:#11109. -- Ticket URL: https://issues.apache.org/bloodhound/ticket/457#comment:5 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #438: Implement and enforce product permission policy
#438: Implement and enforce product permission policy ---+-- Reporter: olemis| Owner: jure Type: task | Status: review Priority: critical | Milestone: Release 6 Component: multiproduct |Version: Resolution:| Keywords: permission security bep-0003 ---+-- Comment (by jure): t438_r1457691_cpmngr_xtpt.diff applied in t1458170. -- Ticket URL: https://issues.apache.org/bloodhound/ticket/438#comment:10 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #438: Implement and enforce product permission policy
#438: Implement and enforce product permission policy ---+-- Reporter: olemis| Owner: jure Type: task | Status: closed Priority: critical | Milestone: Release 6 Component: multiproduct |Version: Resolution: fixed | Keywords: permission security bep-0003 ---+-- Changes (by jure): * status: review = closed * resolution: = fixed -- Ticket URL: https://issues.apache.org/bloodhound/ticket/438#comment:11 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #466: Add a dismiss button to widget_alert
#466: Add a dismiss button to widget_alert --+-- Reporter: rjollos | Owner: rjollos Type: enhancement | Status: new Priority: minor| Milestone: Release 6 Component: ui design|Version: Resolution: | Keywords: widget bootstrap --+-- Comment (by jdreimann): I've got no issues with this. -- Ticket URL: https://issues.apache.org/bloodhound/ticket/466#comment:3 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #462: Move attachments include out of the main ticket form
#462: Move attachments include out of the main ticket form +--- Reporter: gjm| Owner: gjm Type: defect | Status: closed Priority: blocker| Milestone: Release 5 Component: dashboard |Version: Resolution: fixed | Keywords: +--- Changes (by gjm): * status: accepted = closed * resolution: = fixed Comment: calling this fixed -- Ticket URL: https://issues.apache.org/bloodhound/ticket/462#comment:3 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #472: Compatibility with trac search
#472: Compatibility with trac search --+ Reporter: astaric | Owner: nobody Type: enhancement | Status: new Priority: major| Milestone: Component: search |Version: Resolution: | Keywords: bep-0004 bep-0004-beta --+ Comment (by andrej): Fixed in r1458321 with patch form astaric. -- Ticket URL: https://issues.apache.org/bloodhound/ticket/472#comment:1 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #473: Improve basic details on ticket page and page structure
#473: Improve basic details on ticket page and page structure --+--- Reporter: gjm | Owner: gjm Type: enhancement | Status: accepted Priority: major| Milestone: Release 6 Component: dashboard|Version: Resolution: | Keywords: --+--- Changes (by gjm): * status: new = accepted * owner: = gjm * component: = dashboard * milestone: = Release 6 -- Ticket URL: https://issues.apache.org/bloodhound/ticket/473#comment:1 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #325: Multiproduct UI: Dashboard
#325: Multiproduct UI: Dashboard --+--- Reporter: peter| Owner: matevzb Type: enhancement | Status: assigned Priority: major| Milestone: Release 6 Component: dashboard|Version: Resolution: | Keywords: --+--- Comment (by matevzb): Fixed My Tickets and Active Tickets in r1458416 - introduced !ProductQueryModule (based on trac's !QueryModule), which uses !ProductQuery instead of Query. -- Ticket URL: https://issues.apache.org/bloodhound/ticket/325#comment:7 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #473: Improve basic details on ticket page and page structure
#473: Improve basic details on ticket page and page structure
--+---
Reporter: gjm | Owner: gjm
Type: enhancement | Status: accepted
Priority: major| Milestone: Release 6
Component: dashboard|Version:
Resolution: | Keywords:
--+---
Comment (by gjm):
r1458370 changes the way the summary updates the form to allow larger
changes in page structure
r1458386 moves, shortens and tidies up the basic ticket details so that
they only show the ticket number, the assigned to and last opened details
r1458401 moves the ticket summary above the two column layout to be full
width ({{{.span12}}})
r1458413 restructures the page, creating a new {{{div.row}} to contain all
the non activity items in the left column and allow the activity column to
be full height
r1458420 moves the help notice so it is also in the left hand column
--
Ticket URL: https://issues.apache.org/bloodhound/ticket/473#comment:2
Apache Bloodhound https://issues.apache.org/bloodhound/
The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #449: Expand sticky header to work across all screens
#449: Expand sticky header to work across all screens --+--- Reporter: gjm | Owner: gjm Type: enhancement | Status: accepted Priority: major| Milestone: Release 6 Component: dashboard|Version: Resolution: | Keywords: --+--- Changes (by gjm): * status: new = accepted * owner: = gjm * component: = dashboard * milestone: = Release 6 -- Ticket URL: https://issues.apache.org/bloodhound/ticket/449#comment:1 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #438: Implement and enforce product permission policy
#438: Implement and enforce product permission policy ---+- Reporter: olemis| Owner: jure Type: task | Status: review Priority: critical | Milestone: Release 6 Component: multiproduct |Version: Resolution:| Keywords: permission security ---+- Comment (by jure): t438_r1456016_product_perms.diff applied in r1457686. -- Ticket URL: https://issues.apache.org/bloodhound/ticket/438#comment:4 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #404: Populate default schema on product addition
#404: Populate default schema on product addition ---+--- Reporter: jure | Owner: jure Type: defect| Status: assigned Priority: major | Milestone: Release 6 Component: multiproduct |Version: Resolution:| Keywords: bep-0003 multiproduct ---+--- Comment (by jure): t404_r1456016_revert_r1449636.diff applied in r1457691. -- Ticket URL: https://issues.apache.org/bloodhound/ticket/404#comment:9 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #404: Populate default schema on product addition
#404: Populate default schema on product addition ---+--- Reporter: jure | Owner: jure Type: defect| Status: closed Priority: major | Milestone: Release 6 Component: multiproduct |Version: Resolution: fixed | Keywords: bep-0003 multiproduct ---+--- Changes (by jure): * status: assigned = closed * resolution: = fixed -- Ticket URL: https://issues.apache.org/bloodhound/ticket/404#comment:10 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #438: Implement and enforce product permission policy
#438: Implement and enforce product permission policy
---+-
Reporter: olemis| Owner: olemis
Type: task | Status: assigned
Priority: critical | Milestone: Release 6
Component: multiproduct |Version:
Resolution:| Keywords: permission security
---+-
Changes (by jure):
* status: review = assigned
* owner: jure = olemis
Comment:
Patch applied, causes this failure in test suite:
{{{
==
ERROR: test_available_actions_isolation
(tests.ticket.api.ProductTicketSystemTestCase)
--
Traceback (most recent call last):
File /path/to/bloodhound/bloodhound_multiproduct/tests/ticket/api.py,
line 81, in test_available_actions_isolation
self.assertEqual(['leave'], self._get_actions({'status': 'closed'}))
File /path/to/bloodhound/trac/trac/ticket/tests/api.py, line 25, in
_get_actions
return ts.get_available_actions(self.req, Ticket(self.env, id))
File /path/to/bloodhound/trac/trac/ticket/api.py, line 267, in
get_available_actions
weighted_actions = controller.get_ticket_actions(req, ticket) or []
File /path/to/bloodhound/trac/trac/ticket/default_workflow.py, line
192, in get_ticket_actions
if self._is_action_allowed(ticket_perm, required_perms):
File /path/to/bloodhound/trac/trac/ticket/default_workflow.py, line
206, in _is_action_allowed
if permission in ticket_perm:
File /path/to/bloodhound/trac/trac/perm.py, line 556, in
has_permission
return self._has_permission(action, resource)
File /path/to/bloodhound/trac/trac/perm.py, line 570, in
_has_permission
check_permission(action, perm.username, resource, perm)
File /path/to/bloodhound/trac/trac/perm.py, line 462, in
check_permission
perm)
File /path/to/bloodhound/trac/trac/perm.py, line 296, in
check_permission
get_user_permissions(username)
File /path/to/bloodhound/trac/trac/perm.py, line 391, in
get_user_permissions
actions = self.get_actions_dict()
File /path/to/bloodhound/trac/trac/perm.py, line 359, in
get_actions_dict
for requestor in self.requestors:
File /path/to/bloodhound/trac/trac/core.py, line 78, in extensions
components = [component.compmgr[cls] for cls in classes]
File /path/to/bloodhound/trac/trac/core.py, line 215, in __getitem__
component = cls(self)
File
/path/to/bloodhound/bloodhound_multiproduct/multiproduct/cache.py, line
54, in wrapper
key = keymap(args, kwds, kwd_mark)
File /path/to/bloodhound/bloodhound_multiproduct/multiproduct/env.py,
line 347, in product_env_keymap
if isinstance(args[1], Product):
IndexError: tuple index out of range
}}}
--
Ticket URL: https://issues.apache.org/bloodhound/ticket/438#comment:5
Apache Bloodhound https://issues.apache.org/bloodhound/
The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #390: Product wiki syntax
#390: Product wiki syntax -+- Reporter: olemis | Owner: jure Type: task| Status: closed Priority: major | Milestone: Release 6 Component: |Version: multiproduct | Keywords: product resource wiki syntax Resolution: fixed | TracLinks -+- Changes (by jure): * status: assigned = closed * resolution: = fixed -- Ticket URL: https://issues.apache.org/bloodhound/ticket/390#comment:25 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #438: Implement and enforce product permission policy
#438: Implement and enforce product permission policy ---+- Reporter: olemis| Owner: olemis Type: task | Status: assigned Priority: critical | Milestone: Release 6 Component: multiproduct |Version: Resolution:| Keywords: permission security ---+- Comment (by jure): Patch also breaks dispatching process as `PermissionSystem.get_actions_dict` (that traverses through requestors) attempts to instantiate `ProductEnvironment` w/o product parameter causing `product_env_keymap` to fail in the exact same location as during test suite run. Workaround is to remove `IPermissionRequestor` from the list of interfaces implemented by `ProductEnvironment`. -- Ticket URL: https://issues.apache.org/bloodhound/ticket/438#comment:6 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
