Re: [Apache Bloodhound] #508: Trac plugin does not working in the Bloodhound Theme
#508: Trac plugin does not working in the Bloodhound Theme
+
Reporter: goody80| Owner: nobody
Type: defect | Status: new
Priority: major | Milestone:
Component: dashboard |Version: 0.5.3
Resolution: | Keywords:
+
Comment (by goody80):
* Please find attach with below error message
* [[Image(https://issues.apache.org/bloodhound/raw-
attachment/ticket/508/TicketCreateError.jpg)]]
{{{
2013-04-25 18:07:18,858 Trac[theme] ERROR: BH: Quick create ticket failed
PRIMARY KEY must be unique
Traceback (most recent call last):
File /data/bloodhound/installer/bloodhound/lib/python2.6/site-
packages/bhtheme/theme.py, line 424, in process_request
ticket_id = self.create(req, summary, desc, attrs, True)
File /data/bloodhound/installer/bloodhound/lib/python2.6/site-
packages/bhtheme/theme.py, line 460, in create
listener.ticket_created(t)
File /usr/lib/python2.6/site-packages/TracBacklog-0.4.0_dev-
py2.6.egg/backlog/web_ui.py, line 180, in ticket_created
(ticket.id, rank))
File /data/bloodhound/installer/bloodhound/lib/python2.6/site-
packages/trac/db/util.py, line 65, in execute
return self.cursor.execute(sql_escape_percent(sql), args)
File /data/bloodhound/installer/bloodhound/lib/python2.6/site-
packages/trac/db/sqlite_backend.py, line 78, in execute
result = PyFormatCursor.execute(self, *args)
File /data/bloodhound/installer/bloodhound/lib/python2.6/site-
packages/trac/db/sqlite_backend.py, line 56, in execute
args or [])
File /data/bloodhound/installer/bloodhound/lib/python2.6/site-
packages/trac/db/sqlite_backend.py, line 48, in _rollback_on_error
return function(self, *args, **kwargs)
IntegrityError: PRIMARY KEY must be unique
}}}
Thanks :)
Ralf.
--
Ticket URL: https://issues.apache.org/bloodhound/ticket/508#comment:9
Apache Bloodhound https://issues.apache.org/bloodhound/
The Apache Bloodhound issue tracker
svn commit: r1475690 - in /bloodhound/trunk/bloodhound_multiproduct: multiproduct/api.py tests/upgrade.py
Author: astaric
Date: Thu Apr 25 10:21:14 2013
New Revision: 1475690
URL: http://svn.apache.org/r1475690
Log:
Move/copy attachment files when migrating attachments during the upgrade.
Modified:
bloodhound/trunk/bloodhound_multiproduct/multiproduct/api.py
bloodhound/trunk/bloodhound_multiproduct/tests/upgrade.py
Modified: bloodhound/trunk/bloodhound_multiproduct/multiproduct/api.py
URL:
http://svn.apache.org/viewvc/bloodhound/trunk/bloodhound_multiproduct/multiproduct/api.py?rev=1475690r1=1475689r2=1475690view=diff
==
--- bloodhound/trunk/bloodhound_multiproduct/multiproduct/api.py (original)
+++ bloodhound/trunk/bloodhound_multiproduct/multiproduct/api.py Thu Apr 25
10:21:14 2013
@@ -20,11 +20,13 @@
import copy
import os
+import shutil
from genshi.builder import tag, Element
from genshi.core import escape, Markup, unescape
from pkg_resources import resource_filename
+from trac.attachment import Attachment
from trac.config import Option, PathOption
from trac.core import Component, TracError, implements, Interface
from trac.db import Table, Column, DatabaseManager, Index
@@ -284,6 +286,14 @@ class MultiProductSystem(Component):
self.log.info(Migrating tickets w/o product to default
product)
db(UPDATE ticket SET product='%s'
WHERE (product IS NULL OR product='') %
DEFAULT_PRODUCT)
+self._migrate_attachments(
+db(SELECT a.type, a.id, a.filename
+FROM attachment a
+ INNER JOIN ticket t ON a.id = %(t.id)s
+ WHERE a.type='ticket'
+% {'t.id': db.cast('t.id', 'text')}),
+to_product=DEFAULT_PRODUCT
+)
self.log.info(Migrating ticket tables to a new schema)
for table in TICKET_TABLES:
@@ -370,19 +380,39 @@ class MultiProductSystem(Component):
wiki_name=wiki_name,
old_product=wiki_product,
new_product=product.prefix))
+self._migrate_attachments(
+db(SELECT type, id, filename
+FROM attachment
+ WHERE type='wiki'
+ AND id='%s'
+ AND product='%s'
+% (wiki_name, DEFAULT_PRODUCT)),
+to_product=DEFAULT_PRODUCT,
+copy=True
+)
else:
self.log.info(Moving wiki page '%s' to default
product, wiki_name)
db(UPDATE wiki
SET product='%s'
- WHERE name='%s' AND version=%s AND
product='%s' %
- (DEFAULT_PRODUCT,
- wiki_name, wiki_version, wiki_product))
+ WHERE name='%s' AND version=%s AND product='%s'
+% (DEFAULT_PRODUCT,
+ wiki_name, wiki_version, wiki_product))
db(UPDATE attachment
SET product='%s'
WHERE type='wiki'
AND id='%s'
AND product='%s'
% (DEFAULT_PRODUCT, wiki_name, wiki_product))
+self._migrate_attachments(
+db(SELECT type, id, filename
+FROM attachment
+ WHERE type='wiki'
+ AND id='%s'
+ AND product='%s'
+% (wiki_name, DEFAULT_PRODUCT)),
+to_product=DEFAULT_PRODUCT,
+)
+
drop_temp_table(temp_table_name)
# soft link existing repositories to default product
@@ -434,6 +464,39 @@ class MultiProductSystem(Component):
self.env.enable_multiproduct_schema(True)
+def _migrate_attachments(self, attachments, to_product=None, copy=False):
+for type, id, filename in attachments:
+old_path = Attachment._get_path(self.env.path, type, id, filename)
+new_path = self.env.path
+if to_product:
+new_path = os.path.join(new_path, 'products', to_product)
+new_path = Attachment._get_path(new_path, type, id, filename)
+dirname = os.path.dirname(new_path)
+if not os.path.exists(old_path):
+self.log.warning(
+
svn commit: r1475716 - /bloodhound/trunk/bloodhound_multiproduct/multiproduct/web_ui.py
Author: matevz
Date: Thu Apr 25 11:50:09 2013
New Revision: 1475716
URL: http://svn.apache.org/r1475716
Log:
Ref. #441, exception raised when browsing to /products/
Modified:
bloodhound/trunk/bloodhound_multiproduct/multiproduct/web_ui.py
Modified: bloodhound/trunk/bloodhound_multiproduct/multiproduct/web_ui.py
URL:
http://svn.apache.org/viewvc/bloodhound/trunk/bloodhound_multiproduct/multiproduct/web_ui.py?rev=1475716r1=1475715r2=1475716view=diff
==
--- bloodhound/trunk/bloodhound_multiproduct/multiproduct/web_ui.py (original)
+++ bloodhound/trunk/bloodhound_multiproduct/multiproduct/web_ui.py Thu Apr 25
11:50:09 2013
@@ -67,7 +67,7 @@ class ProductModule(Component):
if 'PRODUCT_VIEW' in req.perm(Neighborhood('product',
p.prefix))]
-if pid is not None:
+if pid:
add_link(req, 'up', req.href.products(), _('Products'))
try:
@@ -90,7 +90,7 @@ class ProductModule(Component):
elif action == 'delete':
raise TracError(_('Product removal is not allowed!'))
-if pid is None:
+if not pid:
data = {'products': products,
'context': web_context(req, Resource('product', None))}
return 'product_list.html', data, None
[Apache Bloodhound] BloodhoundContributing modified
Page BloodhoundContributing was changed by jdreimann Diff URL: https://issues.apache.org/bloodhound/wiki/BloodhoundContributing?action=diffversion=18 Revision 18 Comment: Added Google Summer of Code section Changes: ---8--8--8--8--8--8--8--8 Index: BloodhoundContributing = --- BloodhoundContributing (version: 17) +++ BloodhoundContributing (version: 18) @@ -48,6 +48,10 @@ The BloodhoundDevGuide should also be a good resource for those who want to get more involved in the project. +== Google Summer of Code == + +We're taking part in the [http://www.google-melange.com/gsoc/homepage/google/gsoc2013 2013 Google Summer of Code] through the [http://www.apache.org/ ASF], and have got several [goo.gl/qTKKQ project suggestions] that students can draw inspiration from. You are welcome to suggest your own idea too, please get in touch via our mailing list, more information on that here: BloodhoundContactInfo + == Contributing [wiki:Ui Designs] == This project has a strong focus on usability. How to use the application should be obvious, even for novice users. We believe that the application can go a long way towards helping people become intermediate users quickly too. ---8--8--8--8--8--8--8--8 -- Page URL: https://issues.apache.org/bloodhound/wiki/BloodhoundContributing 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 'BloodhoundContributing' page. If it was not you, please report to .
[Apache Bloodhound] BloodhoundContributing modified
Page BloodhoundContributing was changed by jdreimann Diff URL: https://issues.apache.org/bloodhound/wiki/BloodhoundContributing?action=diffversion=19 Revision 19 Comment: Fixed broken link for GSoC suggestions Changes: ---8--8--8--8--8--8--8--8 Index: BloodhoundContributing = --- BloodhoundContributing (version: 18) +++ BloodhoundContributing (version: 19) @@ -50,7 +50,7 @@ == Google Summer of Code == -We're taking part in the [http://www.google-melange.com/gsoc/homepage/google/gsoc2013 2013 Google Summer of Code] through the [http://www.apache.org/ ASF], and have got several [goo.gl/qTKKQ project suggestions] that students can draw inspiration from. You are welcome to suggest your own idea too, please get in touch via our mailing list, more information on that here: BloodhoundContactInfo +We're taking part in the [http://www.google-melange.com/gsoc/homepage/google/gsoc2013 2013 Google Summer of Code] through the [http://www.apache.org/ ASF], and have got several [http://goo.gl/qTKKQ project suggestions] that students can draw inspiration from. You are welcome to suggest your own idea too, please get in touch via our mailing list, more information on that here: BloodhoundContactInfo == Contributing [wiki:Ui Designs] == ---8--8--8--8--8--8--8--8 -- Page URL: https://issues.apache.org/bloodhound/wiki/BloodhoundContributing 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 'BloodhoundContributing' page. If it was not you, please report to .
[Apache Bloodhound] New user registration: Pranayb
New user registration for user Pranayb -- Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound issue tracker
[Apache Bloodhound] BloodhoundContributing modified
Page BloodhoundContributing was changed by gjm
Diff URL:
https://issues.apache.org/bloodhound/wiki/BloodhoundContributing?action=diffversion=20
Revision 20
Comment: adding hints for checking out the source code and notes on running
with multiple databases
Changes:
---8--8--8--8--8--8--8--8
Index: BloodhoundContributing
=
--- BloodhoundContributing (version: 19)
+++ BloodhoundContributing (version: 20)
@@ -14,31 +14,69 @@
Apache Bloodhound is written in Python and so, if you have already
successfully installed Bloodhound, you will probably have all that you need to
develop it too.
-BloodhoundInstall and BloodhoundDetailedInstallation both provide information
about installing but, if you already have Python, python-setuptools, python-pip
and python-virtualenv, installation can be achieved as follows:
+The latest version of the source code is available from the ASF's subversion
repository at [https://svn.apache.org/repos/asf/bloodhound/trunk/]. In order to
get the code from here, you will require a subversion client. For linux users
there will certainly be a command line client in your distribution's
repositories (e.g. {{{sudo apt-get install subversion}}} or {{{sudo yum install
subversion}}}). For most platforms there should be various graphical programs
that will also work (e.g. SmartSVN or TortoiseSVN) and it is also possible that
the IDE that you choose to program with will also have subversion integration.
See http://en.wikipedia.org/wiki/Comparison_of_Subversion_clients for more
information on these choices.
+
+While the subversion repository is where committers are expected to submit
their code, there is also an official mirror of the repositories on GitHub
https://github.com/apache/bloodhound which provides an alternative if you
prefer using git. Git, of course, requires its own client programs to be
installed on your computer.
+
+If you choose to checkout from the subversion repository you can do this:
+{{{
+#!sh
+svn co https://svn.apache.org/repos/asf/bloodhound/trunk/ bloodhound
+}}}
+
+Using git you would instead:
+{{{
+#!sh
+git clone https://github.com/apache/bloodhound.git
+}}}
+
+BloodhoundInstall and BloodhoundDetailedInstallation both provide information
about installing but, if you already have Python, python-setuptools, python-pip
and python-virtualenv, installation proceed as follows:
{{{
-svn co https://svn.apache.org/repos/asf/bloodhound/trunk/ bloodhound
+#!sh
+virtualenv bh
+source bh/bin/activate
cd bloodhound/installer
-virtualenv bloodhound
-source bloodhound/bin/activate
pip install -r requirements-dev.txt
-python bloodhound_setup.py --database-type=sqlite --admin-user=admin
--admin-password=adminpasswd
+}}}
+
+To complete the setup, the easiest option is to use the SQLite database:
+{{{
+#!sh
+python bloodhound_setup.py --project=sqlite --database-type=sqlite
--admin-user=admin --admin-password=adminpasswd
}}}
after which you can run the standalone server:
{{{
-tracd -r --port=8000 bloodhound/environments/main
+#!sh
+tracd -r --port=8000 bloodhound/environments/sqlite
}}}
With this method of installation, the Bloodhound and Trac code is run direct
from the checked out code. Any source code for external dependencies and
plugins meanwhile will be found in {{{../installer/bloodhound/src/}}}.
-You should find that when you make changes to the associated source code, when
using the {{{-r}}} option on {{{tracd}}}, the server will reload and the edited
code will be run instead of the original. In order to get templates to reload
after modifications are made, you can edit
{{{bloodhound/environments/main/conf/trac.ini}}} and add the following line to
the {{{[trac]}}} section:
+It is also possible to run multiple environments at once from the {{{tracd}}}
development server. This means that if you have also created a PostgreSQL
database for testing you can setup a new environment with the command:
+{{{
+#!sh
+python bloodhound_setup.py --project=postgres --database-type=postgres -u
bloodhound -p bloodhound --admin-user=admin --admin-password=adminpasswd
+}}}
+
+and if all everything is set up properly you will be able to run both
environments with:
+{{{
+#!sh
+tracd -r --port=8000 bloodhound/environments/sqlite
bloodhound/environments/postgres
+}}}
+
+This is particularly useful for making sure that changes that involve database
interactions work for all the databases we support.
+
+You should find that when you make changes to the associated source code, when
using the {{{-r}}} option on {{{tracd}}}, the server will reload and the edited
code will be run instead of the original. In order to get templates to reload
after modifications are made, you can edit
{{{bloodhound/environments/main/sqlite/trac.ini}}} and add the following line
to the {{{[trac]}}} section:
{{{
#!ini
auto_reload = true
}}}
+
+and repeat
Re: [Apache Bloodhound] #509: Test compatibility with XMLRPC Plug-in
#509: Test compatibility with XMLRPC Plug-in ---+-- Reporter: mbooth| Owner: olemis Type: task | Status: accepted Priority: critical | Milestone: Component: plugins |Version: Resolution:| Keywords: rpc XmlRpcPlugin ---+-- Comment (by olemis): Replying to [comment:5 mbooth]: So does this need fixing in Bloodhound or the plug-in? Accurate answers will be available once a resolution is found . At least for moment the I'm working on a fork of XmlRpcPlugin (namely BloodhoundRPC plugin) . Depending on the nature of the changes needed , different things might happen . If you need to patch the plug-in do you think it is feasible to make one branch of code work in both Trac and Bloodhound/MultiProduct? (The upstream maintainer may be more willing to take the patch...) I'm co-maintainer of XmlRpcPlugin but I do not have commit access to plugin's svn area @ t.h.o , only the maintainer . AFAICT , I'm not sure it will be easy to push Bloodhound-specific patches to distribute them with mainstream XmlRpcPlugin , at least until they prove to play nice with Trac as well . But the fact is that e.g. the testing environment is completely different , it's an extra maintenance overhead , etc ... Or will it be necessary to fork? ... so I just [https://bitbucket.org/olemis/bloodhound-rpc forked XmlRpcPlugin @ Bitbucket] ;) PS: We can try other alternatives later . -- Ticket URL: https://issues.apache.org/bloodhound/ticket/509#comment:6 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound issue tracker
[Apache Bloodhound] BloodhoundContributing modified
Page BloodhoundContributing was changed by jdreimann
Diff URL:
https://issues.apache.org/bloodhound/wiki/BloodhoundContributing?action=diffversion=21
Revision 21
Comment: Made some text changes and styling of links.
Changes:
---8--8--8--8--8--8--8--8
Index: BloodhoundContributing
=
--- BloodhoundContributing (version: 20)
+++ BloodhoundContributing (version: 21)
@@ -14,11 +14,15 @@
Apache Bloodhound is written in Python and so, if you have already
successfully installed Bloodhound, you will probably have all that you need to
develop it too.
-The latest version of the source code is available from the ASF's subversion
repository at [https://svn.apache.org/repos/asf/bloodhound/trunk/]. In order to
get the code from here, you will require a subversion client. For linux users
there will certainly be a command line client in your distribution's
repositories (e.g. {{{sudo apt-get install subversion}}} or {{{sudo yum install
subversion}}}). For most platforms there should be various graphical programs
that will also work (e.g. SmartSVN or TortoiseSVN) and it is also possible that
the IDE that you choose to program with will also have subversion integration.
See http://en.wikipedia.org/wiki/Comparison_of_Subversion_clients for more
information on these choices.
+The source code is available from the ASF's subversion repository at
[https://svn.apache.org/repos/asf/bloodhound/trunk/]. To get the code, you need
a [http://en.wikipedia.org/wiki/Apache_Subversion Subversion] client.
+- Linux: There will be a command line client in your distribution's
repositories (e.g. {{{sudo apt-get install subversion}}} or {{{sudo yum install
subversion}}}).
+- Windows: [http://tortoisesvn.net/ TortoiseSVN], [http://smartsvn.com/
SmartSVN] or [http://en.wikipedia.org/wiki/Comparison_of_Subversion_clients
others]
+- Mac OS X: [http://smartsvn.com/ SmartSVN], [http://versionsapp.com/
Versions] or [http://en.wikipedia.org/wiki/Comparison_of_Subversion_clients
others]
+The IDE that you choose to program with may also have subversion integration.
-While the subversion repository is where committers are expected to submit
their code, there is also an official mirror of the repositories on GitHub
https://github.com/apache/bloodhound which provides an alternative if you
prefer using git. Git, of course, requires its own client programs to be
installed on your computer.
+While the subversion repository is where committers are expected to submit
their code, there is also [https://github.com/apache/bloodhound an official
mirror of the repository on GitHub] which provides an alternative if you prefer
using git. Git, of course, requires its own client programs to be installed on
your computer.
-If you choose to checkout from the subversion repository you can do this:
+To check out the subversion repository you can do this:
{{{
#!sh
svn co https://svn.apache.org/repos/asf/bloodhound/trunk/ bloodhound
---8--8--8--8--8--8--8--8
--
Page URL: https://issues.apache.org/bloodhound/wiki/BloodhoundContributing
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 'BloodhoundContributing' page.
If it was not you, please report to .
Re: [Apache Bloodhound] #509: Test compatibility with XMLRPC Plug-in
#509: Test compatibility with XMLRPC Plug-in ---+-- Reporter: mbooth| Owner: olemis Type: task | Status: accepted Priority: critical | Milestone: Component: plugins |Version: Resolution:| Keywords: rpc XmlRpcPlugin ---+-- Comment (by mbooth): Cool, thanks for your work on this. I'm actually okay with a fork as long as the XML-RPC API remains unchanged. There is already a lot of software out there that talks to Trac programatically and it would be great if it all could also talk to Bloodhound without change -- it would greatly lower the barrier to adoption :-) -- Ticket URL: https://issues.apache.org/bloodhound/ticket/509#comment:7 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound issue tracker
Re: [Apache Bloodhound] #509: Test compatibility with XMLRPC Plug-in
#509: Test compatibility with XMLRPC Plug-in ---+-- Reporter: mbooth| Owner: olemis Type: task | Status: accepted Priority: critical | Milestone: Component: plugins |Version: Resolution:| Keywords: rpc XmlRpcPlugin ---+-- Comment (by olemis): Replying to [comment:5 mbooth]: [...] If you need to patch the plug-in do you think it is feasible to make one branch of code work in both Trac and Bloodhound/MultiProduct? [...] All I can say now , beyond previous comments , is that a solution for #504 has to implemented in order to make this happen . -- Ticket URL: https://issues.apache.org/bloodhound/ticket/509#comment:8 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound issue tracker
Re: [Apache Bloodhound] #508: Trac plugin does not working in the Bloodhound Theme
#508: Trac plugin does not working in the Bloodhound Theme
+
Reporter: goody80| Owner: nobody
Type: defect | Status: new
Priority: major | Milestone:
Component: dashboard |Version: 0.5.3
Resolution: | Keywords:
+
Comment (by olemis):
Thanks for providing further details . Please see inline comments .
Replying to [comment:9 goody80]:
[...]
{{{
2013-04-25 18:07:18,858 Trac[theme] ERROR: BH: Quick create ticket
failed PRIMARY KEY must be unique
Traceback (most recent call last):
File /data/bloodhound/installer/bloodhound/lib/python2.6/site-
packages/bhtheme/theme.py, line 424, in process_request
ticket_id = self.create(req, summary, desc, attrs, True)
File /data/bloodhound/installer/bloodhound/lib/python2.6/site-
packages/bhtheme/theme.py, line 460, in create
listener.ticket_created(t)
}}}
Up to this point this only means that ticket was successfully created and
thereby ticket listeners will be notified of the fact ...
{{{
File /usr/lib/python2.6/site-packages/TracBacklog-0.4.0_dev-
py2.6.egg/backlog/web_ui.py, line 180, in ticket_created
(ticket.id, rank))
File /data/bloodhound/installer/bloodhound/lib/python2.6/site-
packages/trac/db/util.py, line 65, in execute
return self.cursor.execute(sql_escape_percent(sql), args)
}}}
trachacks:BacklogPlugin being one such listener subsequently executing an
(undisclosed) SQL query ...
{{{
File /data/bloodhound/installer/bloodhound/lib/python2.6/site-
packages/trac/db/sqlite_backend.py, line 78, in execute
result = PyFormatCursor.execute(self, *args)
File /data/bloodhound/installer/bloodhound/lib/python2.6/site-
packages/trac/db/sqlite_backend.py, line 56, in execute
args or [])
File /data/bloodhound/installer/bloodhound/lib/python2.6/site-
packages/trac/db/sqlite_backend.py, line 48, in _rollback_on_error
return function(self, *args, **kwargs)
IntegrityError: PRIMARY KEY must be unique
}}}
... that fails when being processed by Trac DB API modules . So this may
be one of four options
1. An error in trachacks:BacklogPlugin
2. An error in Trac DB API
3. An error caused by a modification we made in Trac DB API
4. Interactions between activated components thus causing this error
Could you please mention if you get the same error using /newticket form ?
--
Ticket URL: https://issues.apache.org/bloodhound/ticket/508#comment:10
Apache Bloodhound https://issues.apache.org/bloodhound/
The Apache Bloodhound issue tracker
Re: [Apache Bloodhound] #508: Trac backlog plugin does not working in the Bloodhound Theme (was: Trac plugin does not working in the Bloodhound Theme)
#508: Trac backlog plugin does not working in the Bloodhound Theme + Reporter: goody80| Owner: nobody Type: defect | Status: new Priority: major | Milestone: Component: dashboard |Version: 0.5.3 Resolution: | Keywords: + -- Ticket URL: https://issues.apache.org/bloodhound/ticket/508#comment:11 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound issue tracker
Re: [Apache Bloodhound] #508: Trac backlog plugin does not working in the Bloodhound Theme
#508: Trac backlog plugin does not working in the Bloodhound Theme --+--- Reporter: goody80 | Owner: nobody Type: defect | Status: new Priority: major| Milestone: Component: plugins |Version: 0.5.3 Resolution: | Keywords: BacklogPlugin --+--- Changes (by olemis): * keywords: = BacklogPlugin * component: dashboard = plugins -- Ticket URL: https://issues.apache.org/bloodhound/ticket/508#comment:12 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound issue tracker
Re: [Apache Bloodhound] #508: Trac backlog plugin does not working in the Bloodhound Theme
#508: Trac backlog plugin does not working in the Bloodhound Theme --+--- Reporter: goody80 | Owner: nobody Type: defect | Status: new Priority: major| Milestone: Component: plugins |Version: 0.5.3 Resolution: | Keywords: BacklogPlugin --+--- Comment (by goody80): Thanks for your reply exactly Olemis :) -- Ticket URL: https://issues.apache.org/bloodhound/ticket/508#comment:13 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound issue tracker
[Apache Bloodhound] New user registration: dpanada
New user registration for user dpanada -- Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound issue tracker
