svn commit: r1573926 - in /bloodhound/trunk/bloodhound_theme/bhtheme/htdocs: bloodhound.css js/theme.js

[asemonella]

Author: asemonella
Date: Tue Mar  4 08:15:13 2014
New Revision: 1573926

URL: http://svn.apache.org/r1573926
Log:
#727 Disable "More fields" link instead of hiding
when no product selected.

Modified:
bloodhound/trunk/bloodhound_theme/bhtheme/htdocs/bloodhound.css
bloodhound/trunk/bloodhound_theme/bhtheme/htdocs/js/theme.js

Modified: bloodhound/trunk/bloodhound_theme/bhtheme/htdocs/bloodhound.css
URL: 
http://svn.apache.org/viewvc/bloodhound/trunk/bloodhound_theme/bhtheme/htdocs/bloodhound.css?rev=1573926&r1=1573925&r2=1573926&view=diff
==
--- bloodhound/trunk/bloodhound_theme/bhtheme/htdocs/bloodhound.css (original)
+++ bloodhound/trunk/bloodhound_theme/bhtheme/htdocs/bloodhound.css Tue Mar  4 
08:15:13 2014
@@ -342,8 +342,10 @@ ol.arabic { list-style-type: decimal
  margin-top: 5px;
  margin-bottom: 5px;
 }
-#qct-more {
- visibility: hidden;
+#qct-more.disabled {
+ text-decoration: none;
+ background-color: #fff;
+ color: #333;
 }
 
 /*

Modified: bloodhound/trunk/bloodhound_theme/bhtheme/htdocs/js/theme.js
URL: 
http://svn.apache.org/viewvc/bloodhound/trunk/bloodhound_theme/bhtheme/htdocs/js/theme.js?rev=1573926&r1=1573925&r2=1573926&view=diff
==
--- bloodhound/trunk/bloodhound_theme/bhtheme/htdocs/js/theme.js (original)
+++ bloodhound/trunk/bloodhound_theme/bhtheme/htdocs/js/theme.js Tue Mar  4 
08:15:13 2014
@@ -97,7 +97,7 @@ $(function() {
   /**
* POST QCT form fields to full ticket form when "More fields" is clicked
*/
-  $('#qct-more').click(function(e) {
+  function post_qct_more(e) {
 // As we're not creating the ticket, we'll remove hidden fields
 // that result in unnecessary validation messages.
 e.preventDefault();
@@ -109,21 +109,28 @@ $(function() {
 $qct_form.append('');
 $qct_form.submit();
 
-  });
+  };
 
-  function set_qct_more_visibility(is_visible) {
-if (is_visible) {
-  $('#qct-more').css('visibility', 'visible');
+  function set_qct_more_enabled(is_enabled) {
+var qct_more = $('#qct-more');
+qct_more.unbind('click');
+if (is_enabled) {
+  qct_more.removeClass('disabled');
+  qct_more.click(post_qct_more);
 } else {
-  $('#qct-more').css('visibility', 'hidden');
+  qct_more.addClass('disabled');
+  qct_more.click(function(e) {
+e.preventDefault();
+e.stopPropagation(); // keep #qct-form open
+  });
 }
   }
 
   $('#field-product').change(function(e) {
-set_qct_more_visibility($(this).val());
+set_qct_more_enabled($(this).val());
   });
 
-  set_qct_more_visibility($('#field-product').val());
+  set_qct_more_enabled($('#field-product').val());
 
   $('body').on('click.close', '#qct-alert-close',
   function(e) {

Re: [Apache Bloodhound] #727: Handle long free text entries in sending qct fields to newticket interface

[Apache Bloodhound]

#727: Handle long free text entries in sending qct fields to newticket interface
--+---
  Reporter:  gjm  |  Owner:  antony
  Type:  enhancement  | Status:  accepted
  Priority:  major|  Milestone:  Release 8
 Component:  dashboard|Version:
Resolution:   |   Keywords:
--+---

Comment (by antony):

 Replying to [comment:13 rjollos]:
 > Sorry that I didn't get to review this sooner. There is a regressions in
 r1570616: the product at scope is no longer the default selection.
 >
 > The best way I could see to fix this is with some refactoring, so I hope
 it doesn't seem like I'm trying to hijack your ticket, but since we are
 nearing a release it's probably easiest if I just push the fix and ask for
 feedback (particularly testing).
 >
 > What do you think about having the //More fields// link visible but
 disabled, rather than initially hidden? Actually, the only case that it
 will be hidden on page load is at global scope when `[ticket]
 default_product` hasn't been set, so it's probably not worth spending too
 much time refining.
 >
 > Minor things:
 >  * Python source code should wrap on 79 characters. Additional style
 guidelines that we follow can be found at trac:TracDev/CodingStyle.
 >  * !JavaScript code uses two-space indentation.

 Hello the changes look good to me.
 r1573926 now 'disables' the "More fields" link instead of hiding it.

-- 
Ticket URL: 
Apache Bloodhound 
The Apache Bloodhound issue tracker

Re: [Apache Bloodhound] #769: Move multiproduct changes from trac.resource to multiproduct.resource (was: Move multiproduct changes to resource module from trac.resource to multiproduct.resource)

[Apache Bloodhound]

#769: Move multiproduct changes from trac.resource to multiproduct.resource
---+---
  Reporter:  rjollos   |  Owner:  rjollos
  Type:  enhancement   | Status:  new
  Priority:  major |  Milestone:  Release 8
 Component:  multiproduct  |Version:
Resolution:|   Keywords:
---+---

-- 
Ticket URL: 
Apache Bloodhound 
The Apache Bloodhound issue tracker

[Apache Bloodhound] New user registration: mbrownnyc

[Apache Bloodhound]

New user registration for user mbrownnyc

--
Apache Bloodhound 
The Apache Bloodhound issue tracker

[Apache Bloodhound] #777: User restriction to only tickets they open?

[Apache Bloodhound]

#777: User restriction to only tickets they open?
--+---
  Reporter:  mbrownnyc|Owner:
  Type:  enhancement  |   Status:  new
  Priority:  major|  Version:
Resolution:   |
--+---
 Summary:
 I would like to give end users the ability to create tickets.
 I would like to restrict each user to only see tickets they have opened
 (or followed).

 I would like a user's workflow to be as follows:
 1) User access bloodhound site
 2) user logs on (authing with LDAP)
 3) user is either greeted with "new issue" page, or with the list of their
 current tickets.

 Thanks!


 Robusto:
 [08:25]  I would like the infrastructure team to be able to
 open tickets, and associate them with a project
 [08:25]  but I would like only tickets they open be visible to
 them
 [08:25]  (for instance)
 [08:26]  also front line support has no issue tracker, and I
 would like users to be able to open tickets by accessing bloodhound simply
 [08:26]  so none of those users would be able to see any
 tickets but their own
 [08:26]  interesting
 [08:27]  also, can you confirm that bloodhound can use trac
 "plugins" (interested in email related issue management, and LDAP auth)
 [08:27]  at my last place I used redmine for this whole thing
 [08:27]  but bloodhound seems to be a bit of a better choice
 [08:27]  we are attempting to maintain the ability to use trac
 plugins
 [08:28]  i don't deal with software engineering here, nor did I
 there
 [08:28]  so i suppose it is an interesting use case :)
 [08:28]  cool... I believe I saw plugins that do both of those
 things I mentioned
 [08:28]  that is good
 [08:28]  any idea if the role based access as it exists will do
 what I'd like?
 [08:29]  though if we have not already looked at them, they may
 need some extra work on our part to get them working
 [08:29]  cool
 [08:29]  I'll see as I move forward
 [08:30]  so, I think that you will probably be able to restrict
 with role based access as you say if I understand it
 [08:30]  per user might be a bit more interesting
 [08:30]  I'm less concerned with the infrastructure team, but
 the users simply won't use the system if it's complex
 [08:30]  they'll continue to email, and then no one can track
 issues, and produce reports
 [08:30]  yeah
 [08:31]  hmm
 [08:31]  I should try to get backup into this conversation!
 [08:31]  do you think I can work out a workflow like: user
 accesses URL, user logs on with LDAP creds, use either sees list of opened
 issues, or user is greeted with "new issue"?
 [08:32]  I have not seen such use before
 [08:33]  I don't *think* that would currently be possible
 [08:33]  might be worth raising a ticket with us to ask for it
 [08:34]  cool, will do

-- 
Ticket URL: 
Apache Bloodhound 
The Apache Bloodhound issue tracker

Re: [Apache Bloodhound] #777: User restriction to only tickets they open?

[Apache Bloodhound]

#777: User restriction to only tickets they open?
--+
  Reporter:  mbrownnyc|  Owner:  nobody
  Type:  enhancement  | Status:  new
  Priority:  major|  Milestone:
 Component:  dashboard|Version:
Resolution:   |   Keywords:
--+
Changes (by rjollos):

 * owner:   => nobody
 * component:   => dashboard


Comment:

 Replying to [ticket:777 mbrownnyc]:
 > 3) user is either greeted with "new issue" page, or with the list of
 their current tickets.

 This can be done by setting the `[trac] default_handler` option in the
 environment's `conf/trac.ini` file.

 {{{#!ini
 [trac]
 default_handler = ProductTicketModule
 }}}
 will result in the landing page being `/newticket`.

 {{{#!ini
 [trac]
 default_handler = ProductQueryModule
 }}}
 will result in the landing page being `/query`.

 {{{#!ini
 [trac]
 default_handler = DashboardModule
 }}}
 will result in the landing page being `/dashboard`.

 It appears that we don't have a way to set the `default_handler` for each
 product. As far as I can see, only a global setting is allowed at this
 time, meaning each product will have the same landing page that as we have
 at global scope.

 As to your question about restricting users to only see tickets they have
 reported, that is possible but a little more complex. I'll follow-up on
 that question soon.

-- 
Ticket URL: 
Apache Bloodhound 
The Apache Bloodhound issue tracker

[Apache Bloodhound] #778: Ticket cannot be found if reporter is not an active user

[Apache Bloodhound]

#778: Ticket cannot be found if reporter is not an active user
-+-
  Reporter:  hb  |Owner:
  Type:  defect  |   Status:  new
  Priority:  major   |  Version:  0.7.0
Resolution:  |
-+-
 Case:
 user X reports a ticket
 user X gets removed from user base

 Result:
 Tickets created by that user can no longer be found via search.

-- 
Ticket URL: 
Apache Bloodhound 
The Apache Bloodhound issue tracker

Re: [Apache Bloodhound] #759: Incorrect translation when switching language

[Apache Bloodhound]

#759: Incorrect translation when switching language
---+--
  Reporter:  SaintGermain  |  Owner:  nobody
  Type:  defect| Status:  new
  Priority:  minor |  Milestone:
 Component:  trac core |Version:  0.8.0dev
Resolution:|   Keywords:  i18n
---+--
Changes (by rjollos):

 * component:  dashboard => trac core


Comment:

 I've seen this issue in Trac, and created a ticket for the issue:
 trac:#11515. Please confirm whether that ticket adequately captures the
 issue you are reporting here.

-- 
Ticket URL: 
Apache Bloodhound 
The Apache Bloodhound issue tracker

Re: [Apache Bloodhound] #761: Duplicate ticket id can't be added in batch modify

[Apache Bloodhound]

#761: Duplicate ticket id can't be added in batch modify
+--
  Reporter:  rjollos|  Owner:  nobody
  Type:  defect | Status:  new
  Priority:  major  |  Milestone:  next 0.x
 Component:  trac core  |Version:
Resolution: |   Keywords:  batch modify
+--
Description changed by rjollos:

Old description:

> The ITicketManipulator interface isn't called when batch modifying
> tickets, so the duplicate attribute doesn't get added to the ticket
> object and ticket validation is not performed. A workaround was put in
> place in #710 ([1538891]).
>
> See also #742.

New description:

 The ITicketManipulator interface isn't called when batch modifying
 tickets, so the duplicate attribute doesn't get added to the ticket
 object, ticket validation is skipped and the ticket relation is not added.
 A workaround was put in place in #710 ([1538891]) to avoid a traceback,
 but it does nothing to solve the underlying problem.

 The issue has previously been discussed on the
 [http://markmail.org/message/4mjt2jmwxk3326qa mailing list]. See also
 #742.

--

-- 
Ticket URL: 
Apache Bloodhound 
The Apache Bloodhound issue tracker

Re: [Apache Bloodhound] #778: Ticket cannot be found if reporter is not an active user

[Apache Bloodhound]

#778: Ticket cannot be found if reporter is not an active user
+
  Reporter:  hb |  Owner:  nobody
  Type:  defect | Status:  new
  Priority:  major  |  Milestone:
 Component:  dashboard  |Version:  0.7.0
Resolution: |   Keywords:
+
Changes (by rjollos):

 * owner:   => nobody
 * component:   => dashboard


Comment:

 Replying to [ticket:778 hb]:
 > Case:
 > user X reports a ticket
 > user X gets removed from user base

 More specifically, what do you mean by "removed from user base", and what
 are the steps to "remove from user base"? Delete the user account?

 > Result:
 > Tickets created by that user can no longer be found via search.

 Just to be clear, you are referring to search (`/search`) and not ticket
 query?

-- 
Ticket URL: 
Apache Bloodhound 
The Apache Bloodhound issue tracker

Re: [Apache Bloodhound] #724: Sub-query links in ticket group stats widget

[Apache Bloodhound]

#724: Sub-query links in ticket group stats widget
-+-
  Reporter:  olemis  |  Owner:  nobody
  Type:  | Status:  new
  enhancement|  Milestone:
  Priority:  trivial |Version:  0.7.0
 Component:  dashboard   |   Keywords:  milestone product dashboard,
Resolution:  |  starter
-+-

Comment (by rjollos):

 Thanks. I had been incorrectly grep'ing for `TicketGroupStatsWidget`.

 One of the GSoC applicants was asking about this ticket on the
 [http://markmail.org/message/hkh6o7ontnlgumnl mailing list]. If you could
 add some additional details to help with reproducing and fixing the issue,
 that would be much appreciated.

-- 
Ticket URL: 
Apache Bloodhound 
The Apache Bloodhound issue tracker

Re: [Apache Bloodhound] #777: User restriction to only tickets they open?

[Apache Bloodhound]

#777: User restriction to only tickets they open?
--+
  Reporter:  mbrownnyc|  Owner:  nobody
  Type:  enhancement  | Status:  new
  Priority:  major|  Milestone:
 Component:  dashboard|Version:
Resolution:   |   Keywords:
--+

Comment (by olemis):

 You have some options to set product configuration e.g. default handler

   1. `trac-admin product admin  config set  ...`
  * see comment:1
   2. via web admin UI after installing a plugin e.g. th:IniAdminPlugin

 Nevertheless this process may be too tedious in practice *if* the
 configuration varies among products so you could also create a .ini file
 with a given set of optios and make a set of products inherit them
 according to your expectations by executing `trac-admin product admin
  config set trac inherit
 /path/to/globalenv/config/trac.ini,/path/to/yourcfg.ini`

-- 
Ticket URL: 
Apache Bloodhound 
The Apache Bloodhound issue tracker

Re: [Apache Bloodhound] #777: User restriction to only tickets they open?

[Apache Bloodhound]

#777: User restriction to only tickets they open?
--+
  Reporter:  mbrownnyc|  Owner:  nobody
  Type:  enhancement  | Status:  new
  Priority:  major|  Milestone:
 Component:  dashboard|Version:
Resolution:   |   Keywords:
--+

Comment (by olemis):

 Replying to [ticket:777 mbrownnyc]:
 > Summary:
 > I would like to give end users the ability to create tickets.
 > I would like to restrict each user to only see tickets they have opened
 (or followed).
 >

 About this, it seems to me your use case looks close to a help desk
 system. We've deployed a few instances for this purpose but always
 activating a custom permission policy component. I'm not sure of whether
 there's such feature available on trac-hacks.org

 [...]

-- 
Ticket URL: 
Apache Bloodhound 
The Apache Bloodhound issue tracker

[Apache Bloodhound] WikiStart modified

[Apache Bloodhound]

Page "WikiStart" was changed by rjollos
Diff URL: 

Revision 42
Comment: We need a more prominent link to the registration page. Users 
repeatedly ask on the mailing list how to register for an account. However, 
that is blocked by the need to upgrade i.a.o, so it appears the best we can do 
for now is to add a link on WikiStart. See also #628.
Changes:
---8<--8<--8<--8<--8<--8<--8<--8<
Index: WikiStart
=
--- WikiStart (version: 41)
+++ WikiStart (version: 42)
@@ -43,6 +43,8 @@
 
 You can also connect with the Bloodhound community through the IRC channel 
([irc://irc.freenode.net/bloodhound #bloodhound on irc.freenode.net]).
 
+[/register Registering]  for an account in the Bloodhound issue tracker allows 
creating and commenting on tickets.
+
 -
 == Useful links ==
  * TitleIndex: Complete list of the local wiki pages
---8<--8<--8<--8<--8<--8<--8<--8<

--
Page URL: 
Apache Bloodhound 
The Apache Bloodhound 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] #771: Improve test case coverage for trac-admin command

[Apache Bloodhound]

#771: Improve test case coverage for trac-admin command
---+
  Reporter:  rjollos   |  Owner:  nobody
  Type:  defect| Status:  new
  Priority:  major |  Milestone:  Release 9
 Component:  multiproduct  |Version:
Resolution:|   Keywords:  trac-1.0.2
---+

Comment (by rjollos):

 There was nothing wrong with the patches in #756 and #757. The reason I
 reworked the patches in #756 and #757 was to try and document some issues
 with the current testing approach. The patch in this ticket is not quite
 ready yet, one issue being the ambiguity with `config` that you mentioned,
 but what I hope to do is provide full coverage for the `trac-admin`
 commands in Trac, and then find a way to utilize these tests in Bloodhound
 in the product context, executing them in the same way that they'd be
 executed from the command line, with as little duplication of test code as
 possible between Trac and Bloodhound.

-- 
Ticket URL: 
Apache Bloodhound 
The Apache Bloodhound issue tracker

Re: [Apache Bloodhound] #775: Can't create multiple "is a parent of" relations

[Apache Bloodhound]

#775: Can't create multiple "is a parent of" relations
+
  Reporter:  rjollos|  Owner:  rjollos
  Type:  defect | Status:  accepted
  Priority:  major  |  Milestone:  Release 8
 Component:  relations  |Version:
Resolution: |   Keywords:  validation
+
Changes (by rjollos):

 * status:  new => accepted
 * keywords:   => validation


-- 
Ticket URL: 
Apache Bloodhound 
The Apache Bloodhound issue tracker

Re: [Apache Bloodhound] #777: User restriction to only tickets they open?

[Apache Bloodhound]

#777: User restriction to only tickets they open?
--+
  Reporter:  mbrownnyc|  Owner:  nobody
  Type:  enhancement  | Status:  new
  Priority:  major|  Milestone:
 Component:  dashboard|Version:
Resolution:   |   Keywords:
--+

Comment (by rjollos):

 Replying to [ticket:777 mbrownnyc]:
 > I would like to restrict each user to only see tickets they have opened
 (or followed).

 The requirement //user can only see tickets for which they are the
 reporter// is clear. However, I'm not sure what you mean by **(or
 followed)**. How would a user follow tickets for which they are not the
 reporter, if they can only view tickets for which they are the reporter?
 Are you suggesting that the user should see tickets when other users add
 them to the Cc field of the ticket?

 th:PrivateTicketsPlugin seems like a close fit to what you are requesting,
 however the performance of the plugin is poor due to some architectural
 issues in Trac. With just a few dozens users I've seen the ticket page
 load times increase by more than 5 seconds.

-- 
Ticket URL: 
Apache Bloodhound 
The Apache Bloodhound issue tracker

Re: [Apache Bloodhound] #776: The validation error messages in bhrelations.validation should be marked as translatable strings

[Apache Bloodhound]

#776: The validation error messages in bhrelations.validation should be marked 
as
translatable strings
+--
  Reporter:  rjollos|  Owner:  nobody
  Type:  defect | Status:  new
  Priority:  major  |  Milestone:  next 0.x
 Component:  relations  |Version:
Resolution: |   Keywords:  i18n
+--
Changes (by rjollos):

 * keywords:   => i18n


-- 
Ticket URL: 
Apache Bloodhound 
The Apache Bloodhound issue tracker

Re: [Apache Bloodhound] #772: Many multiproduct test modules can't be executed in isolation

[Apache Bloodhound]

#772: Many multiproduct test modules can't be executed in isolation
---+
  Reporter:  rjollos   |  Owner:  olemis
  Type:  defect| Status:  new
  Priority:  major |  Milestone:  next 0.x
 Component:  multiproduct  |Version:
Resolution:|   Keywords:  unit tests
---+
Changes (by rjollos):

 * keywords:   => unit tests
 * milestone:   => next 0.x


-- 
Ticket URL: 
Apache Bloodhound 
The Apache Bloodhound issue tracker

Re: [Apache Bloodhound] #770: Location of test cases for bloodhound_multiproduct is not consistent with other projects

[Apache Bloodhound]

#770: Location of test cases for bloodhound_multiproduct is not consistent with
other projects
---+-
  Reporter:  rjollos   |  Owner:  nobody
  Type:  defect| Status:  new
  Priority:  major |  Milestone:  Unscheduled
 Component:  multiproduct  |Version:
Resolution:|   Keywords:  test cases
---+-
Changes (by rjollos):

 * keywords:   => test cases
 * milestone:   => Unscheduled


-- 
Ticket URL: 
Apache Bloodhound 
The Apache Bloodhound issue tracker

Re: [Apache Bloodhound] #769: Move multiproduct changes from trac.resource to multiproduct.resource

[Apache Bloodhound]

#769: Move multiproduct changes from trac.resource to multiproduct.resource
---+-
  Reporter:  rjollos   |  Owner:  rjollos
  Type:  enhancement   | Status:  new
  Priority:  major |  Milestone:  Release 8
 Component:  multiproduct  |Version:
Resolution:|   Keywords:  refactoring
---+-
Changes (by rjollos):

 * keywords:   => refactoring


-- 
Ticket URL: 
Apache Bloodhound 
The Apache Bloodhound issue tracker

Re: [Apache Bloodhound] #771: Improve test case coverage for trac-admin command

[Apache Bloodhound]

#771: Improve test case coverage for trac-admin command
---+
  Reporter:  rjollos   |  Owner:  nobody
  Type:  enhancement   | Status:  new
  Priority:  major |  Milestone:  Release 9
 Component:  multiproduct  |Version:
Resolution:|   Keywords:  trac-1.0.2
---+
Changes (by rjollos):

 * type:  defect => enhancement


-- 
Ticket URL: 
Apache Bloodhound 
The Apache Bloodhound issue tracker

Re: [Apache Bloodhound] #776: The validation error messages in bhrelations.validation should be marked as translatable strings

[Apache Bloodhound]

#776: The validation error messages in bhrelations.validation should be marked 
as
translatable strings
--+--
  Reporter:  rjollos  |  Owner:  nobody
  Type:  enhancement  | Status:  new
  Priority:  major|  Milestone:  next 0.x
 Component:  relations|Version:
Resolution:   |   Keywords:  i18n
--+--
Changes (by rjollos):

 * type:  defect => enhancement


-- 
Ticket URL: 
Apache Bloodhound 
The Apache Bloodhound issue tracker

Re: [Apache Bloodhound] #764: Global commands should be filtered from product-scope help, and product-scope commands filtered from global help

[Apache Bloodhound]

#764: Global commands should be filtered from product-scope help, and product-
scope commands filtered from global help
---+
  Reporter:  rjollos   |  Owner:  olemis
  Type:  defect| Status:  assigned
  Priority:  major |  Milestone:  next 0.x
 Component:  multiproduct  |Version:
Resolution:|   Keywords:  product admin help
---+
Changes (by rjollos):

 * keywords:  product admin => product admin help
 * milestone:   => next 0.x


-- 
Ticket URL: 
Apache Bloodhound 
The Apache Bloodhound issue tracker

Re: [Apache Bloodhound] #767: CalDAV integration

[Apache Bloodhound]

#767: CalDAV integration
--+-
  Reporter:  gjm  |  Owner:  nobody
  Type:  enhancement  | Status:  new
  Priority:  major|  Milestone:  Unscheduled
 Component:  dashboard|Version:
Resolution:   |   Keywords:
--+-
Changes (by rjollos):

 * owner:   => nobody
 * component:   => dashboard
 * milestone:   => Unscheduled


-- 
Ticket URL: 
Apache Bloodhound 
The Apache Bloodhound issue tracker

Re: [Apache Bloodhound] #762: UnboundLocalError from trac-admin console command

[Apache Bloodhound]

#762: UnboundLocalError from trac-admin console command
+--
  Reporter:  rjollos|  Owner:  rjollos
  Type:  defect | Status:  assigned
  Priority:  minor  |  Milestone:  Release 9
 Component:  trac core  |Version:  0.8.0dev
Resolution: |   Keywords:  admin console trac-1.0.2
+--
Changes (by rjollos):

 * component:  multiproduct => trac core


-- 
Ticket URL: 
Apache Bloodhound 
The Apache Bloodhound issue tracker

Re: [Apache Bloodhound] #759: Incorrect translation when switching language

[Apache Bloodhound]

#759: Incorrect translation when switching language
---+-
  Reporter:  SaintGermain  |  Owner:  nobody
  Type:  defect| Status:  new
  Priority:  minor |  Milestone:  Release 9
 Component:  trac core |Version:  0.8.0dev
Resolution:|   Keywords:  i18n trac-1.0.2
---+-
Changes (by rjollos):

 * keywords:  i18n => i18n trac-1.0.2
 * milestone:   => Release 9


-- 
Ticket URL: 
Apache Bloodhound 
The Apache Bloodhound issue tracker

Re: [Apache Bloodhound] #758: Part of message not displayed after translation

[Apache Bloodhound]

#758: Part of message not displayed after translation
---+--
  Reporter:  SaintGermain  |  Owner:  nobody
  Type:  defect| Status:  new
  Priority:  minor |  Milestone:  next 0.x
 Component:  trac core |Version:  0.8.0dev
Resolution:|   Keywords:  i18n
---+--
Changes (by rjollos):

 * component:  dashboard => trac core
 * milestone:   => next 0.x


-- 
Ticket URL: 
Apache Bloodhound 
The Apache Bloodhound issue tracker

Re: [Apache Bloodhound] #760: Improve i18n

[Apache Bloodhound]

#760: Improve i18n
---+--
  Reporter:  SaintGermain  |  Owner:  nobody
  Type:  enhancement   | Status:  new
  Priority:  minor |  Milestone:  next 0.x
 Component:  dashboard |Version:  0.8.0dev
Resolution:|   Keywords:  i18n
---+--
Changes (by rjollos):

 * milestone:   => next 0.x


-- 
Ticket URL: 
Apache Bloodhound 
The Apache Bloodhound issue tracker

Re: [Apache Bloodhound] #763: l10n files need license headers

[Apache Bloodhound]

#763: l10n files need license headers
+
  Reporter:  rjollos|  Owner:  rjollos
  Type:  task   | Status:  new
  Priority:  major  |  Milestone:  next 0.x
 Component:  trac core  |Version:  0.8.0dev
Resolution: |   Keywords:  license babel i18n
+
Changes (by rjollos):

 * keywords:  license => license babel i18n


Comment:

 As mentioned on the [http://markmail.org/message/qul7qalbyozpsyrh mailing
 list], a [https://github.com/mitsuhiko/babel/issues/82 ticket] has been
 opened in the Babel issue tracker for the feature request.

-- 
Ticket URL: 
Apache Bloodhound 
The Apache Bloodhound issue tracker

Re: [Apache Bloodhound] #731: CommitTicketUpdater in multi-repository environment - after #695

[Apache Bloodhound]

#731: CommitTicketUpdater in multi-repository environment - after #695
-+-
  Reporter:  olemis  |  Owner:  nobody
  Type:  | Status:  new
  enhancement|  Milestone:  next 0.x
  Priority:  major   |Version:
 Component:  |   Keywords:  commit ticket updater, vcs, hg, git
  multiproduct   |
Resolution:  |
-+-
Changes (by rjollos):

 * milestone:   => next 0.x


-- 
Ticket URL: 
Apache Bloodhound 
The Apache Bloodhound issue tracker

Re: [Apache Bloodhound] #747: Test env's quick_create_ticket method unusable

[Apache Bloodhound]

#747: Test env's quick_create_ticket method unusable
--+--
  Reporter:  olemis   |  Owner:  antony
  Type:  enhancement  | Status:  assigned
  Priority:  minor|  Milestone:  next 0.x
 Component:  dashboard|Version:  0.8.0dev
Resolution:   |   Keywords:  qa, js
--+--
Description changed by rjollos:

Old description:

> The helper method
> [source:trunk/bloodhound_multiproduct/tests/functional/__init__.py@1557944:628-649
> quick_create_ticket] seems not to work with recent js-based
> implementation of QCT form .

New description:

 The helper method
 
[source:trunk/bloodhound_multiproduct/tests/functional/__init__.py@1557944:628-649
 quick_create_ticket] in `BloodhoundFunctionalTester` seems not to work
 with recent js-based implementation of QCT form .

--

-- 
Ticket URL: 
Apache Bloodhound 
The Apache Bloodhound issue tracker

Re: [Apache Bloodhound] #753: Crash when Whoosh backend crash

[Apache Bloodhound]

#753: Crash when Whoosh backend crash
---+-
  Reporter:  SaintGermain  |  Owner:  nobody
  Type:  enhancement   | Status:  new
  Priority:  minor |  Milestone:  Unscheduled
 Component:  search|Version:  0.8.0dev
Resolution:|   Keywords:
---+-
Changes (by rjollos):

 * milestone:   => Unscheduled


-- 
Ticket URL: 
Apache Bloodhound 
The Apache Bloodhound issue tracker

Re: [Apache Bloodhound] #729: Wrap author information for ticket change comments in a span to make them stylable

[Apache Bloodhound]

#729: Wrap author information for ticket change comments in a span to make them
stylable
--+--
  Reporter:  rjollos  |  Owner:  nobody
  Type:  enhancement  | Status:  new
  Priority:  major|  Milestone:  next 1.x
 Component:  trac core|Version:
Resolution:   |   Keywords:  trac-1.2
--+--
Changes (by rjollos):

 * milestone:   => next 1.x


-- 
Ticket URL: 
Apache Bloodhound 
The Apache Bloodhound issue tracker

Re: [Apache Bloodhound] #728: Set default component to empty string

[Apache Bloodhound]

#728: Set default component to empty string
--+--
  Reporter:  rjollos  |  Owner:  nobody
  Type:  enhancement  | Status:  new
  Priority:  major|  Milestone:  next 1.x
 Component:  trac core|Version:
Resolution:   |   Keywords:  trac-1.2
--+--
Changes (by rjollos):

 * milestone:   => next 1.x


-- 
Ticket URL: 
Apache Bloodhound 
The Apache Bloodhound issue tracker

Re: [Apache Bloodhound] #726: Error occurs during changeset indexing (0.8-dev)

[Apache Bloodhound]

#726: Error occurs during changeset indexing (0.8-dev)
---+-
  Reporter:  olemis|  Owner:  nobody
  Type:  defect| Status:  new
  Priority:  critical  |  Milestone:  next 0.x
 Component:  search|Version:
Resolution:|   Keywords:  vcs hooks, search index
---+-
Changes (by rjollos):

 * milestone:   => next 0.x


-- 
Ticket URL: 
Apache Bloodhound 
The Apache Bloodhound issue tracker

Re: [Apache Bloodhound] #725: Move repository test env ops into separate VCS tester classes

[Apache Bloodhound]

#725: Move repository test env ops into separate VCS tester classes
---+-
  Reporter:  olemis|  Owner:  nobody
  Type:  enhancement   | Status:  new
  Priority:  major |  Milestone:  Unscheduled
 Component:  multiproduct  |Version:  0.7.0
Resolution:|   Keywords:  qa vcs
---+-
Changes (by rjollos):

 * milestone:   => Unscheduled


-- 
Ticket URL: 
Apache Bloodhound 
The Apache Bloodhound issue tracker

Re: [Apache Bloodhound] #719: New components not available immediately in ticket select

[Apache Bloodhound]

#719: New components not available immediately in ticket select
---+
  Reporter:  olemis|  Owner:  nobody
  Type:  defect| Status:  new
  Priority:  critical  |  Milestone:  next 0.x
 Component:  multiproduct  |Version:  0.7.0
Resolution:|   Keywords:  db, sqlite, postgresql
---+
Changes (by rjollos):

 * milestone:   => next 0.x


-- 
Ticket URL: 
Apache Bloodhound 
The Apache Bloodhound issue tracker

Re: [Apache Bloodhound] #715: Functional test cases for dashboard widgets - after #564

[Apache Bloodhound]

#715: Functional test cases for dashboard widgets - after #564
---+---
  Reporter:  olemis|  Owner:  nobody
  Type:  enhancement   | Status:  new
  Priority:  major |  Milestone:  Unscheduled
 Component:  multiproduct  |Version:
Resolution:|   Keywords:  qa, multiproduct, widgets
---+---
Changes (by rjollos):

 * milestone:   => Unscheduled


-- 
Ticket URL: 
Apache Bloodhound 
The Apache Bloodhound issue tracker

Re: [Apache Bloodhound] #692: Increase relevance of ticket status in UI

[Apache Bloodhound]

#692: Increase relevance of ticket status in UI
--+---
  Reporter:  olemis   |  Owner:  nobody
  Type:  enhancement  | Status:  new
  Priority:  minor|  Milestone:  next 0.x
 Component:  ui design|Version:  0.7.0
Resolution:   |   Keywords:  ticket status
--+---
Changes (by rjollos):

 * milestone:   => next 0.x


-- 
Ticket URL: 
Apache Bloodhound 
The Apache Bloodhound issue tracker

Re: [Apache Bloodhound] #703: Hide the retarget select when the milestone has no associated tickets

[Apache Bloodhound]

#703: Hide the retarget select when the milestone has no associated tickets
--+--
  Reporter:  rjollos  |  Owner:  nobody
  Type:  enhancement  | Status:  new
  Priority:  major|  Milestone:  next 1.x
 Component:  ui design|Version:
Resolution:   |   Keywords:  trac-1.2
--+--
Changes (by rjollos):

 * milestone:   => next 1.x


-- 
Ticket URL: 
Apache Bloodhound 
The Apache Bloodhound issue tracker

Re: [Apache Bloodhound] #702: Allow default values for a ticket to be cleared through the ticket admin pages

[Apache Bloodhound]

#702: Allow default values for a ticket to be cleared through the ticket admin
pages
--+--
  Reporter:  rjollos  |  Owner:  nobody
  Type:  enhancement  | Status:  new
  Priority:  major|  Milestone:  next 1.x
 Component:  ui design|Version:
Resolution:   |   Keywords:  trac-1.2
--+--
Changes (by rjollos):

 * milestone:   => next 1.x


-- 
Ticket URL: 
Apache Bloodhound 
The Apache Bloodhound issue tracker

Re: [Apache Bloodhound] #672: Edit ticket relationships

[Apache Bloodhound]

#672: Edit ticket relationships
--+-
  Reporter:  olemis   |  Owner:  nobody
  Type:  enhancement  | Status:  new
  Priority:  minor|  Milestone:  Unscheduled
 Component:  relations|Version:  0.7.0
Resolution:   |   Keywords:  crud
--+-
Changes (by rjollos):

 * milestone:   => Unscheduled


-- 
Ticket URL: 
Apache Bloodhound 
The Apache Bloodhound issue tracker

Re: [Apache Bloodhound] #674: Modify templates to account for implementation of ReadonlyWikiPolicy

[Apache Bloodhound]

#674: Modify templates to account for implementation of ReadonlyWikiPolicy
--+--
  Reporter:  rjollos  |  Owner:  nobody
  Type:  enhancement  | Status:  new
  Priority:  major|  Milestone:  next 1.x
 Component:  trac core|Version:
Resolution:   |   Keywords:  trac-1.2
--+--
Changes (by rjollos):

 * component:  ui design => trac core
 * milestone:   => next 1.x


-- 
Ticket URL: 
Apache Bloodhound 
The Apache Bloodhound issue tracker

Re: [Apache Bloodhound] #675: Allow configuring the default "retargeting" option when closing or deleting a milestone

[Apache Bloodhound]

#675: Allow configuring the default "retargeting" option when closing or 
deleting
a milestone
--+--
  Reporter:  rjollos  |  Owner:  nobody
  Type:  enhancement  | Status:  new
  Priority:  major|  Milestone:  next 1.x
 Component:  ui design|Version:
Resolution:   |   Keywords:  trac-1.2
--+--
Changes (by rjollos):

 * milestone:   => next 1.x


-- 
Ticket URL: 
Apache Bloodhound 
The Apache Bloodhound issue tracker

Re: [Apache Bloodhound] #680: Maintain product-relative scope when switching products through the breadcrumb (was: Ticket breadcrumb)

[Apache Bloodhound]

#680: Maintain product-relative scope when switching products through the
breadcrumb
+--
  Reporter:  ogaerick   |  Owner:  rjollos
  Type:  defect | Status:  accepted
  Priority:  critical   |  Milestone:  next 0.x
 Component:  dashboard  |Version:  0.7.0
Resolution: |   Keywords:
+--

-- 
Ticket URL: 
Apache Bloodhound 
The Apache Bloodhound issue tracker

Re: [Apache Bloodhound] #680: Maintain product-relative scope when switching products through the breadcrumb

[Apache Bloodhound]

#680: Maintain product-relative scope when switching products through the
breadcrumb
+--
  Reporter:  ogaerick   |  Owner:
  Type:  defect | Status:  new
  Priority:  critical   |  Milestone:  next 0.x
 Component:  dashboard  |Version:  0.7.0
Resolution: |   Keywords:
+--
Changes (by rjollos):

 * owner:  rjollos =>
 * status:  accepted => new


-- 
Ticket URL: 
Apache Bloodhound 
The Apache Bloodhound issue tracker

Re: [Apache Bloodhound] #685: IntegrityError: duplicate key value violates unique constraint "permission_pk"DETAIL: Key (username, action, product)=(authenticated, PRODUCT_VIEW, domtracDispatcher) alr

[Apache Bloodhound]

#685: IntegrityError: duplicate key value violates unique constraint
"permission_pk"DETAIL:  Key (username, action, product)=(authenticated,
PRODUCT_VIEW, domtracDispatcher) already exists.
+
  Reporter:  ogaerick   |  Owner:  nobody
  Type:  defect | Status:  new
  Priority:  blocker|  Milestone:  next 0.x
 Component:  dashboard  |Version:  0.7.0
Resolution: |   Keywords:  postgresql
+

Comment (by rjollos):

 This might have the same underlying cause as #681.

-- 
Ticket URL: 
Apache Bloodhound 
The Apache Bloodhound issue tracker

Re: [Apache Bloodhound] #686: Dashboard Milestones and Components

[Apache Bloodhound]

#686: Dashboard Milestones and Components
--+--
  Reporter:  ogaerick |  Owner:  nobody
  Type:  enhancement  | Status:  new
  Priority:  major|  Milestone:  next 0.x
 Component:  dashboard|Version:  0.7.0
Resolution:   |   Keywords:
--+--
Changes (by rjollos):

 * type:  defect => enhancement


-- 
Ticket URL: 
Apache Bloodhound 
The Apache Bloodhound issue tracker

Re: [Apache Bloodhound] #664: Embed buttons for products and milestones cannot be disabled

[Apache Bloodhound]

#664: Embed buttons for products and milestones cannot be disabled
---+--
  Reporter:  antonia.horincar  |  Owner:  antonia.horincar
  Type:  defect| Status:  new
  Priority:  major |  Milestone:  Unscheduled
 Component:  plugins   |Version:
Resolution:|   Keywords:  bep-0007
---+--
Changes (by rjollos):

 * milestone:   => Unscheduled


-- 
Ticket URL: 
Apache Bloodhound 
The Apache Bloodhound issue tracker

Re: [Apache Bloodhound] #660: Integrate changes from Trac 1.0.2

[Apache Bloodhound]

#660: Integrate changes from Trac 1.0.2
+
  Reporter:  rjollos|  Owner:  rjollos
  Type:  task   | Status:  new
  Priority:  major  |  Milestone:  Release 9
 Component:  trac core  |Version:
Resolution: |   Keywords:  trac-1.0.2
+
Changes (by rjollos):

 * type:  defect => task


-- 
Ticket URL: 
Apache Bloodhound 
The Apache Bloodhound issue tracker

[Apache Bloodhound] #779: Integrate changes from Trac 1.2

[Apache Bloodhound]

#779: Integrate changes from Trac 1.2
---+--
 Reporter:  rjollos|  Owner:  nobody
 Type:  task   | Status:  new
 Priority:  major  |  Milestone:  next 1.x
Component:  trac core  |Version:
 Keywords:  trac-1.2   |
---+--
 When Trac 1.2 is released, a number of changes will need to be made to the
 templates, and even some commits to the copy of Trac rolled back. This
 ticket will track the required changes:

 Tickets tracking template changes needed for 1.2:
 [[TicketQuery(keywords~=trac-1.2)]]

-- 
Ticket URL: 
Apache Bloodhound 
The Apache Bloodhound issue tracker

Re: [Apache Bloodhound] #659: Ticket Embed UI Improvements

[Apache Bloodhound]

#659: Ticket Embed UI Improvements
--+-
  Reporter:  jdreimann|  Owner:  jdreimann
  Type:  enhancement  | Status:  assigned
  Priority:  major|  Milestone:  Unscheduled
 Component:  ui design|Version:
Resolution:   |   Keywords:  bep-0007 ticket
--+-
Changes (by rjollos):

 * milestone:  next 0.x => Unscheduled


-- 
Ticket URL: 
Apache Bloodhound 
The Apache Bloodhound issue tracker

Re: [Apache Bloodhound] #656: Neighborhood error

[Apache Bloodhound]

#656: Neighborhood error
---+
  Reporter:  olemis|  Owner:  nobody
  Type:  defect| Status:  new
  Priority:  critical  |  Milestone:  next 0.x
 Component:  multiproduct  |Version:
Resolution:|   Keywords:  resource, neighborhood, config
---+
Changes (by rjollos):

 * milestone:   => next 0.x


-- 
Ticket URL: 
Apache Bloodhound 
The Apache Bloodhound issue tracker

Re: [Apache Bloodhound] #655: Genshi unicode error rendering widget

[Apache Bloodhound]

#655: Genshi unicode error rendering widget
+
  Reporter:  olemis |  Owner:  nobody
  Type:  defect | Status:  new
  Priority:  critical   |  Milestone:  Unscheduled
 Component:  dashboard  |Version:
Resolution: |   Keywords:  genshi unicode
+
Changes (by rjollos):

 * milestone:   => Unscheduled


-- 
Ticket URL: 
Apache Bloodhound 
The Apache Bloodhound issue tracker

Re: [Apache Bloodhound] #651: Multiple commands in single TracAdmin session (functional tests)

[Apache Bloodhound]

#651: Multiple commands in single TracAdmin session (functional tests)
---+-
  Reporter:  olemis|  Owner:  olemis
  Type:  enhancement   | Status:  accepted
  Priority:  minor |  Milestone:  Unscheduled
 Component:  multiproduct  |Version:  0.6.0
Resolution:|   Keywords:  qa admin
---+-
Changes (by rjollos):

 * milestone:  next 0.x => Unscheduled


-- 
Ticket URL: 
Apache Bloodhound 
The Apache Bloodhound issue tracker

Re: [Apache Bloodhound] #647: Can't reassign ticket to another product once assigned to Default (@) product

[Apache Bloodhound]

#647: Can't reassign ticket to another product once assigned to Default (@)
product
---+
  Reporter:  ChrisHarris   |  Owner:  nobody
  Type:  defect| Status:  new
  Priority:  major |  Milestone:  next 0.x
 Component:  multiproduct  |Version:  0.6.0
Resolution:|   Keywords:  ticket product
---+
Changes (by rjollos):

 * milestone:   => next 0.x


-- 
Ticket URL: 
Apache Bloodhound 
The Apache Bloodhound issue tracker

Re: [Apache Bloodhound] #642: Internal server error creating ticket

[Apache Bloodhound]

#642: Internal server error creating ticket
+---
  Reporter:  rimas  |  Owner:
  Type:  defect | Status:  new
  Priority:  major  |  Milestone:
 Component:  trac core  |Version:  0.6.0
Resolution: |   Keywords:  db
+---
Changes (by rjollos):

 * status:  needinfo(new) => new
 * owner:  rimas =>


-- 
Ticket URL: 
Apache Bloodhound 
The Apache Bloodhound issue tracker

Re: [Apache Bloodhound] #642: Internal server error creating ticket

[Apache Bloodhound]

#642: Internal server error creating ticket
+
  Reporter:  rimas  |  Owner:
  Type:  defect | Status:  closed
  Priority:  major  |  Milestone:
 Component:  trac core  |Version:  0.6.0
Resolution:  duplicate  |   Keywords:  db
+
Changes (by rjollos):

 * status:  new => closed
 * resolution:   => duplicate


Comment:

 Closing as duplicate, as suggested in comment:1. Please reopen if you are
 still experiencing the problem in the latest version of Bloodhound.

-- 
Ticket URL: 
Apache Bloodhound 
The Apache Bloodhound issue tracker

Re: [Apache Bloodhound] #620: Issues with TOC macro and PostgreSQL

[Apache Bloodhound]

#620: Issues with TOC macro and PostgreSQL
---+--
  Reporter:  olemis|  Owner:  nobody
  Type:  defect| Status:  new
  Priority:  critical  |  Milestone:
 Component:  plugins   |Version:  0.6.0
Resolution:|   Keywords:  postgresql, db, tocmacro
---+--

Comment (by rjollos):

 Probably the same underlying issue as in #614.

-- 
Ticket URL: 
Apache Bloodhound 
The Apache Bloodhound issue tracker

Re: [Apache Bloodhound] #612: Give components/versions dashboard views

[Apache Bloodhound]

#612: Give components/versions dashboard views
--+--
  Reporter:  mudri|  Owner:  nobody
  Type:  enhancement  | Status:  new
  Priority:  major|  Milestone:  next 1.x
 Component:  dashboard|Version:
Resolution:   |   Keywords:  trac-1.2
--+--
Changes (by rjollos):

 * keywords:   => trac-1.2
 * milestone:   => next 1.x


Comment:

 The changes requested in this ticket will be implemented in trac:#1233,
 which will be included in a 1.1.x release leading up to Trac 1.2.

-- 
Ticket URL: 
Apache Bloodhound 
The Apache Bloodhound issue tracker

Re: [Apache Bloodhound] #610: 'Submit ticket' button at bottom not working in Opera browser

[Apache Bloodhound]

#610: 'Submit ticket' button at bottom not working in Opera browser
+---
  Reporter:  olemis |  Owner:  olemis
  Type:  defect | Status:  needinfo(new)
  Priority:  minor  |  Milestone:  next 0.x
 Component:  ui design  |Version:  0.6.0
Resolution: |   Keywords:  ticket, form, comments, opera
+---
Changes (by rjollos):

 * owner:  nobody => olemis
 * status:  new => needinfo(new)
 * milestone:   => next 0.x


Comment:

 Would you kindly test the latest version of Bloodhound and let us know if
 the issue is still occurring?

-- 
Ticket URL: 
Apache Bloodhound 
The Apache Bloodhound issue tracker

Re: [Apache Bloodhound] #604: Default Product can't be deactivated

[Apache Bloodhound]

#604: Default Product can't be deactivated
---+--
  Reporter:  ogaerick  |  Owner:  nobody
  Type:  defect| Status:  new
  Priority:  critical  |  Milestone:  next 0.x
 Component:  multiproduct  |Version:  0.6.0
Resolution:|   Keywords:
---+--
Changes (by rjollos):

 * milestone:   => next 0.x


-- 
Ticket URL: 
Apache Bloodhound 
The Apache Bloodhound issue tracker

Re: [Apache Bloodhound] #600: dashboard and search/query mismatch WRT all products

[Apache Bloodhound]

#600: dashboard and search/query mismatch WRT all products
-+--
  Reporter:  tim |  Owner:  nobody
  Type:  defect  | Status:  new
  Priority:  major   |  Milestone:  next 0.x
 Component:  search  |Version:  0.6.0
Resolution:  |   Keywords:
-+--
Changes (by rjollos):

 * milestone:   => next 0.x


-- 
Ticket URL: 
Apache Bloodhound 
The Apache Bloodhound issue tracker

Re: [Apache Bloodhound] #641: Decrease logging verbosity

[Apache Bloodhound]

#641: Decrease logging verbosity
---+--
  Reporter:  olemis|  Owner:  nobody
  Type:  enhancement   | Status:  new
  Priority:  minor |  Milestone:  next 0.x
 Component:  multiproduct  |Version:  0.6.0
Resolution:|   Keywords:  logging
---+--
Changes (by rjollos):

 * milestone:   => next 0.x


Comment:

 It would be helpful to know:
  * What logging level you had set.
  * What some of the duplicates are.

-- 
Ticket URL: 
Apache Bloodhound 
The Apache Bloodhound issue tracker

Re: [Apache Bloodhound] #633: Move Bootstrap content to bloodhound_theme

[Apache Bloodhound]

#633: Move Bootstrap content to bloodhound_theme
--+-
  Reporter:  rjollos  |  Owner:  nobody
  Type:  enhancement  | Status:  new
  Priority:  major|  Milestone:  Unscheduled
 Component:  ui design|Version:
Resolution:   |   Keywords:  bootstrap
--+-
Changes (by rjollos):

 * milestone:   => Unscheduled


-- 
Ticket URL: 
Apache Bloodhound 
The Apache Bloodhound issue tracker

Re: [Apache Bloodhound] #620: Issues with TOC macro and PostgreSQL

[Apache Bloodhound]

#620: Issues with TOC macro and PostgreSQL
---+--
  Reporter:  olemis|  Owner:  nobody
  Type:  defect| Status:  new
  Priority:  critical  |  Milestone:  next 0.x
 Component:  plugins   |Version:  0.6.0
Resolution:|   Keywords:  postgresql, db, tocmacro
---+--
Changes (by rjollos):

 * milestone:   => next 0.x


-- 
Ticket URL: 
Apache Bloodhound 
The Apache Bloodhound issue tracker

Re: [Apache Bloodhound] #724: Sub-query links in ticket group stats widget

[Apache Bloodhound]

#724: Sub-query links in ticket group stats widget
-+-
  Reporter:  olemis  |  Owner:  nobody
  Type:  | Status:  new
  enhancement|  Milestone:  Unscheduled
  Priority:  trivial |Version:  0.7.0
 Component:  dashboard   |   Keywords:  milestone product dashboard,
Resolution:  |  starter
-+-
Changes (by rjollos):

 * milestone:   => Unscheduled


-- 
Ticket URL: 
Apache Bloodhound 
The Apache Bloodhound issue tracker

Re: [Apache Bloodhound] #614: Wiki links for new wiki pages take minutes to update

[Apache Bloodhound]

#614: Wiki links for new wiki pages take minutes to update
---+
  Reporter:  olemis|  Owner:  nobody
  Type:  defect| Status:  new
  Priority:  minor |  Milestone:  next 0.x
 Component:  multiproduct  |Version:  0.6.0
Resolution:|   Keywords:  create new wiki, postgresql db
---+
Changes (by rjollos):

 * milestone:   => next 0.x


-- 
Ticket URL: 
Apache Bloodhound 
The Apache Bloodhound issue tracker

Re: [Apache Bloodhound] #602: Allow product to be selected from the new ticket form

[Apache Bloodhound]

#602: Allow product to be selected from the new ticket form
---+---
  Reporter:  ogaerick  |  Owner:  olemis
  Type:  enhancement   | Status:  accepted
  Priority:  critical  |  Milestone:  next 0.x
 Component:  multiproduct  |Version:  0.6.0
Resolution:|   Keywords:  ticket web_ui
---+---

Comment (by rjollos):

 #680 is related - if we continue to use the breadcrumb to switch product
 contexts, then the product-relative scope needs to be maintained. In that
 scenario, we would also need to make sure that fields are forwarded when
 the product is changed.

-- 
Ticket URL: 
Apache Bloodhound 
The Apache Bloodhound issue tracker

[Apache Bloodhound] #780: Workflow transition needinfo -> closed

[Apache Bloodhound]

#780: Workflow transition needinfo -> closed
---+-
 Reporter:  rjollos|  Owner:  nobody
 Type:  defect | Status:  new
 Priority:  major  |  Milestone:  Unscheduled
Component:  siteadmin  |Version:
 Keywords: |
---+-
 In comment:4:ticket:642, I found that it wasn't possible to transition a
 ticket from //needinfo(new)// -> //closed//. The transition
 //needinfo(new)// => //new// was the only allowed transition.

 [[Workflow]]

-- 
Ticket URL: 
Apache Bloodhound 
The Apache Bloodhound issue tracker

Re: [Apache Bloodhound] #610: 'Submit ticket' button at bottom not working in Opera browser

[Apache Bloodhound]

#610: 'Submit ticket' button at bottom not working in Opera browser
+---
  Reporter:  olemis |  Owner:
  Type:  defect | Status:  new
  Priority:  minor  |  Milestone:  next 0.x
 Component:  ui design  |Version:  0.6.0
Resolution: |   Keywords:  ticket, form, comments, opera
+---
Changes (by olemis):

 * status:  needinfo(new) => new
 * owner:  olemis =>


-- 
Ticket URL: 
Apache Bloodhound 
The Apache Bloodhound issue tracker

Re: [Apache Bloodhound] #610: 'Submit ticket' button at bottom not working in Opera browser

[Apache Bloodhound]

#610: 'Submit ticket' button at bottom not working in Opera browser
-+---
  Reporter:  olemis  |  Owner:
  Type:  defect  | Status:  closed
  Priority:  minor   |  Milestone:  next 0.x
 Component:  ui design   |Version:  0.6.0
Resolution:  worksforme  |   Keywords:  ticket, form, comments, opera
-+---
Changes (by olemis):

 * status:  new => closed
 * resolution:   => worksforme


-- 
Ticket URL: 
Apache Bloodhound 
The Apache Bloodhound issue tracker

[Apache Bloodhound] #781: Show product info on global products page

[Apache Bloodhound]

#781: Show product info on global products page
--+--
 Reporter:  rjollos   |  Owner:  nobody
 Type:  enhancement   | Status:  new
 Priority:  major |  Milestone:  next 0.x
Component:  multiproduct  |Version:
 Keywords:|
--+--
 In the Products view (`/product`), the product owner and product
 description should be shown. We may want to have a toggle //Show
 Descriptions//, like on Trac's Reports page.

-- 
Ticket URL: 
Apache Bloodhound 
The Apache Bloodhound issue tracker

[Apache Bloodhound] #782: Inconsistency in requiring owner for product

[Apache Bloodhound]

#782: Inconsistency in requiring owner for product
--+--
 Reporter:  rjollos   |  Owner:  nobody
 Type:  defect| Status:  new
 Priority:  major |  Milestone:  next 0.x
Component:  multiproduct  |Version:
 Keywords:|
--+--
 When creating a product from the //New Product// page
 (`/products?action=new`), an owner is not required. When creating a
 product from the //Manage Products// admin page
 (`/admin/ticket/products`), an owner is required.

-- 
Ticket URL: 
Apache Bloodhound 
The Apache Bloodhound issue tracker

Re: [Apache Bloodhound] #782: Inconsistency in requiring owner for product

[Apache Bloodhound]

#782: Inconsistency in requiring owner for product
---+--
  Reporter:  rjollos   |  Owner:  nobody
  Type:  defect| Status:  new
  Priority:  major |  Milestone:  next 0.x
 Component:  multiproduct  |Version:
Resolution:|   Keywords:
---+--
Description changed by rjollos:

Old description:

> When creating a product from the //New Product// page
> (`/products?action=new`), an owner is not required. When creating a
> product from the //Manage Products// admin page
> (`/admin/ticket/products`), an owner is required.

New description:

 When creating a product from the //New Product// page
 (`/products?action=new`), an owner is not required. When creating a
 product from the //Manage Products// admin page
 (`/admin/ticket/products`), an owner is required.

 Also it should be possible to set the owner from the //New Product// page.
 There is not presently a field for this.

--

-- 
Ticket URL: 
Apache Bloodhound 
The Apache Bloodhound issue tracker

[Apache Bloodhound] #783: Removing product name should not be allowed

[Apache Bloodhound]

#783: Removing product name should not be allowed
--+--
 Reporter:  rjollos   |  Owner:  nobody
 Type:  defect| Status:  new
 Priority:  major |  Milestone:  next 0.x
Component:  multiproduct  |Version:
 Keywords:|
--+--
 The product name cannot be removed when on the //Edit Product// page,
 however the product name can be removed from the //Manage Products// admin
 page. Not surprisingly, when attempting to remove the name from a second
 product, an error results: //You must provide a name for the product//,
 however this is not directly related to the issue at hand.

 There is another inconsistency related to #782. An owner is required when
 creating a product from the //Manage Products// admin page, but we allow
 the owner to be removed when editing the product. We should either not
 require the owner to be set, or not allow it to be removed.

-- 
Ticket URL: 
Apache Bloodhound 
The Apache Bloodhound issue tracker

svn commit: r1574195 - in /bloodhound/trunk: bloodhound_multiproduct/multiproduct/product_admin.py bloodhound_multiproduct/multiproduct/templates/admin_products.html bloodhound_theme/bhtheme/templates

[rjollos]

Author: rjollos
Date: Tue Mar  4 20:50:32 2014
New Revision: 1574195

URL: http://svn.apache.org/r1574195
Log:
0.8dev: When attempting to add a product, preserve form data when a warning is 
raised. Refs #661.

The warning messages were also made more specific.

Modified:
bloodhound/trunk/bloodhound_multiproduct/multiproduct/product_admin.py

bloodhound/trunk/bloodhound_multiproduct/multiproduct/templates/admin_products.html
bloodhound/trunk/bloodhound_theme/bhtheme/templates/bh_admin_products.html

Modified: bloodhound/trunk/bloodhound_multiproduct/multiproduct/product_admin.py
URL: 
http://svn.apache.org/viewvc/bloodhound/trunk/bloodhound_multiproduct/multiproduct/product_admin.py?rev=1574195&r1=1574194&r2=1574195&view=diff
==
--- bloodhound/trunk/bloodhound_multiproduct/multiproduct/product_admin.py 
(original)
+++ bloodhound/trunk/bloodhound_multiproduct/multiproduct/product_admin.py Tue 
Mar  4 20:50:32 2014
@@ -85,6 +85,7 @@ class ProductAdminPanel(TicketAdminPanel
   'description':description,
   'owner':owner,
   }
+data = {}
 
 # Detail view?
 if product:
@@ -105,27 +106,38 @@ class ProductAdminPanel(TicketAdminPanel
 default = self.config.get('ticket', 'default_product')
 if req.method == 'POST':
 # Add Product
-if req.args.get('add') and req.args.get('prefix'):
+if req.args.get('add'):
 req.perm.require('PRODUCT_CREATE')
-if not owner:
-add_warning(req, _('All fields are required!'))
-req.redirect(req.href.admin(cat, page))
-
-try:
-prod = Product(self.env, keys)
-except ResourceNotFound:
-prod = Product(self.env)
-prod.update_field_dict(keys)
-prod.update_field_dict(field_data)
-prod.insert()
-add_notice(req, _('The product "%(id)s" has been 
added.',
-  id=prefix))
-req.redirect(req.href.admin(cat, page))
+if not (prefix and name and owner):
+if not prefix:
+add_warning(req, _("You must provide a prefix "
+   "for the product."))
+if not name:
+add_warning(req, _("You must provide a name "
+   "for the product."))
+if not owner:
+add_warning(req, _("You must provide an owner "
+   "for the product."))
+data['prefix'] = prefix
+data['name'] = name
+data['owner'] = owner
+print data
 else:
-if prod.prefix is None:
-raise TracError(_('Invalid product id.'))
-raise TracError(_("Product %(id)s already exists.",
-  id=prefix))
+try:
+prod = Product(self.env, keys)
+except ResourceNotFound:
+prod = Product(self.env)
+prod.update_field_dict(keys)
+prod.update_field_dict(field_data)
+prod.insert()
+add_notice(req, _('The product "%(id)s" has been '
+  'added.', id=prefix))
+req.redirect(req.href.admin(cat, page))
+else:
+if prod.prefix is None:
+raise TracError(_('Invalid product id.'))
+raise TracError(_("Product %(id)s already exists.",
+  id=prefix))
 
 # Remove product
 elif req.args.get('remove'):
@@ -149,10 +161,9 @@ class ProductAdminPanel(TicketAdminPanel
 _save_config(self.config, req, self.log)
 req.redirect(req.href.admin(cat, page))
 
-products = Product.select(self.env)
-data = {'view': 'list',
-'products': products,
-'default': default}
+data['view'] = 'list'
+data['products'] = Product.select(self.env)
+data['default'] = default
 if self.config.getbool('ticket', 'restrict_owner'):
 perm = PermissionSystem(self.env)
 def valid_owner(username):

Modified: 

Re: [Apache Bloodhound] #661: Loss of user input

[Apache Bloodhound]

#661: Loss of user input
+---
  Reporter:  ralienpp   |  Owner:  rjollos
  Type:  defect | Status:  assigned
  Priority:  major  |  Milestone:  Release 8
 Component:  ui design  |Version:
Resolution: |   Keywords:
+---
Changes (by rjollos):

 * status:  new => assigned
 * owner:  nobody => rjollos
 * milestone:  next 0.x => Release 8


Comment:

 (In [1574195])

 0.8dev: When attempting to add a product, preserve form data when a
 warning is raised. Refs #661.

 The warning messages were also made more specifi

-- 
Ticket URL: 
Apache Bloodhound 
The Apache Bloodhound issue tracker

Re: [Apache Bloodhound] #661: Loss of user input

[Apache Bloodhound]

#661: Loss of user input
---+---
  Reporter:  ralienpp  |  Owner:  rjollos
  Type:  defect| Status:  closed
  Priority:  major |  Milestone:  Release 8
 Component:  multiproduct  |Version:
Resolution:  fixed |   Keywords:  product admin
---+---
Changes (by rjollos):

 * status:  assigned => closed
 * keywords:   => product admin
 * component:  ui design => multiproduct
 * resolution:   => fixed


-- 
Ticket URL: 
Apache Bloodhound 
The Apache Bloodhound issue tracker

svn commit: r1574210 - /bloodhound/trunk/trac/trac/resource.py

[rjollos]

Author: rjollos
Date: Tue Mar  4 21:25:30 2014
New Revision: 1574210

URL: http://svn.apache.org/r1574210
Log:
0.8dev: Part of r1567417. Refs #754.

Modified:
bloodhound/trunk/trac/trac/resource.py

Modified: bloodhound/trunk/trac/trac/resource.py
URL: 
http://svn.apache.org/viewvc/bloodhound/trunk/trac/trac/resource.py?rev=1574210&r1=1574209&r2=1574210&view=diff
==
--- bloodhound/trunk/trac/trac/resource.py (original)
+++ bloodhound/trunk/trac/trac/resource.py Tue Mar  4 21:25:30 2014
@@ -518,7 +518,7 @@ class ResourceSystem(Component):
 """Return a list of all the realm names of neighborhoods."""
 realms = []
 for connector in self.resource_connectors:
-for realm in manager.get_supported_neighborhoods() or []:
+for realm in connector.get_supported_neighborhoods() or []:
 realms.append(realm)
 return realms
 

Re: [Apache Bloodhound] #754: Possible unresolved reference in trac.resource

[Apache Bloodhound]

#754: Possible unresolved reference in trac.resource
+---
  Reporter:  olemis |  Owner:  olemis
  Type:  defect | Status:  closed
  Priority:  minor  |  Milestone:  Release 8
 Component:  trac core  |Version:  0.8.0dev
Resolution:  fixed  |   Keywords:  resource
+---
Changes (by rjollos):

 * status:  new => closed
 * resolution:   => fixed


Comment:

 (In [1574210])

 Part of r1567417. Refs #754.

-- 
Ticket URL: 
Apache Bloodhound 
The Apache Bloodhound issue tracker

svn commit: r1574211 - /bloodhound/trunk/bloodhound_multiproduct/multiproduct/product_admin.py

[rjollos]

Author: rjollos
Date: Tue Mar  4 21:26:39 2014
New Revision: 1574211

URL: http://svn.apache.org/r1574211
Log:
0.8dev: Removed print statement from 1574195.

Modified:
bloodhound/trunk/bloodhound_multiproduct/multiproduct/product_admin.py

Modified: bloodhound/trunk/bloodhound_multiproduct/multiproduct/product_admin.py
URL: 
http://svn.apache.org/viewvc/bloodhound/trunk/bloodhound_multiproduct/multiproduct/product_admin.py?rev=1574211&r1=1574210&r2=1574211&view=diff
==
--- bloodhound/trunk/bloodhound_multiproduct/multiproduct/product_admin.py 
(original)
+++ bloodhound/trunk/bloodhound_multiproduct/multiproduct/product_admin.py Tue 
Mar  4 21:26:39 2014
@@ -121,7 +121,6 @@ class ProductAdminPanel(TicketAdminPanel
 data['prefix'] = prefix
 data['name'] = name
 data['owner'] = owner
-print data
 else:
 try:
 prod = Product(self.env, keys)

Re: [Apache Bloodhound] #721: Crash when clicking on username

[Apache Bloodhound]

#721: Crash when clicking on username
+
  Reporter:  joat   |  Owner:  nobody
  Type:  defect | Status:  new
  Priority:  major  |  Milestone:
 Component:  trac core  |Version:  0.7.0
Resolution: |   Keywords:
+

Comment (by rjollos):

 Thanks for reporting, and sorry it has taken so long to reply.
  * Is this a new installation, or have you previously upgraded from an
 earlier version?
  * Is the !BloodhoundMultiproduct module enabled?

-- 
Ticket URL: 
Apache Bloodhound 
The Apache Bloodhound issue tracker

Re: [Apache Bloodhound] #721: Crash when clicking on username

[Apache Bloodhound]

#721: Crash when clicking on username
+--
  Reporter:  joat   |  Owner:  nobody
  Type:  defect | Status:  new
  Priority:  major  |  Milestone:  next 0.x
 Component:  trac core  |Version:  0.7.0
Resolution: |   Keywords:
+--
Changes (by rjollos):

 * milestone:   => next 0.x


-- 
Ticket URL: 
Apache Bloodhound 
The Apache Bloodhound issue tracker

[Apache Bloodhound] #784: Redirect to wrong location after adding or editing product

[Apache Bloodhound]

#784: Redirect to wrong location after adding or editing product
--+--
 Reporter:  rjollos   |  Owner:  nobody
 Type:  defect| Status:  new
 Priority:  major |  Milestone:  next 0.x
Component:  multiproduct  |Version:
 Keywords:|
--+--
 To reproduce:
  1. Navigate to the //Products// page (`/products`).
  1. Add a new product or edit an existing product.
  1. Submit the form.

 The user is redirected based on the default handler for the product.
 However, the user most likely expects to be redirected back to the
 //Products// page.

-- 
Ticket URL: 
Apache Bloodhound 
The Apache Bloodhound issue tracker

[Apache Bloodhound] #785: Allow default_handler to be set from the Basic Settings admin page

[Apache Bloodhound]

#785: Allow default_handler to be set from the Basic Settings admin page
-+--
 Reporter:  rjollos  |  Owner:  nobody
 Type:  enhancement  | Status:  new
 Priority:  major|  Milestone:  next 1.x
Component:  trac core|Version:
 Keywords:  trac-1.2 |
-+--
 Changes to !BloodhoundTheme templates will be needed after trac:#11519.

 The enhancement request for Trac was created in response to the following
 discussions in Bloodhound:
  * comment:1:ticket:777
  * [http://markmail.org/message/kbnoqjnr3hhi2kus mailing list]t

-- 
Ticket URL: 
Apache Bloodhound 
The Apache Bloodhound issue tracker

Re: [Apache Bloodhound] #679: Add an always-visible link to the products list page

[Apache Bloodhound]

#679: Add an always-visible link to the products list page
--+--
  Reporter:  rjollos  |  Owner:  nobody
  Type:  enhancement  | Status:  new
  Priority:  major|  Milestone:  next 0.x
 Component:  ui design|Version:
Resolution:   |   Keywords:
--+--
Changes (by rjollos):

 * type:  defect => enhancement


-- 
Ticket URL: 
Apache Bloodhound 
The Apache Bloodhound issue tracker

Re: [Apache Bloodhound] #597: Support scripts and extensions in /tracopt

[Apache Bloodhound]

#597: Support scripts and extensions in /tracopt
+-
  Reporter:  olemis |  Owner:  nobody
  Type:  task   | Status:  new
  Priority:  major  |  Milestone:  next 0.x
 Component:  trac core  |Version:
Resolution: |   Keywords:  contrib scripts
+-
Changes (by rjollos):

 * milestone:   => next 0.x


-- 
Ticket URL: 
Apache Bloodhound 
The Apache Bloodhound issue tracker

Re: [Apache Bloodhound] #591: Browse source link for products pointing at invalid URL

[Apache Bloodhound]

#591: Browse source link for products pointing at invalid URL
---+---
  Reporter:  olemis|  Owner:  nobody
  Type:  defect| Status:  new
  Priority:  major |  Milestone:  next 0.x
 Component:  multiproduct  |Version:
Resolution:|   Keywords:  vcs, admin, product, wiki
---+---
Changes (by rjollos):

 * milestone:   => next 0.x


-- 
Ticket URL: 
Apache Bloodhound 
The Apache Bloodhound issue tracker

Re: [Apache Bloodhound] #589: Improve security and verbosity of the "Trac Environment needs to be upgraded" message

[Apache Bloodhound]

#589: Improve security and verbosity of the "Trac Environment needs to be
upgraded" message
--+-
  Reporter:  rjollos  |  Owner:  nobody
  Type:  enhancement  | Status:  new
  Priority:  major|  Milestone:  Unscheduled
 Component:  trac core|Version:
Resolution:   |   Keywords:
--+-
Changes (by rjollos):

 * milestone:   => Unscheduled


-- 
Ticket URL: 
Apache Bloodhound 
The Apache Bloodhound issue tracker

Re: [Apache Bloodhound] #560: Distribution error rendering plugin admin panel

[Apache Bloodhound]

#560: Distribution error rendering plugin admin panel
---+---
  Reporter:  olemis|  Owner:  olemis
  Type:  defect| Status:  needinfo(new)
  Priority:  critical  |  Milestone:
 Component:  search|Version:  0.5.3
Resolution:|   Keywords:  pkg_resources
---+---
Changes (by rjollos):

 * owner:  nobody => olemis
 * status:  new => needinfo(new)


Comment:

 I'm not sure what to do with this ticket in absence of additional info.
 Please try to provide more info on the problem, or close the ticket if the
 issue is no longer reproducible.

-- 
Ticket URL: 
Apache Bloodhound 
The Apache Bloodhound issue tracker

Re: [Apache Bloodhound] #553: Error message can overflow the QCT pop-up

[Apache Bloodhound]

#553: Error message can overflow the QCT pop-up
+-
  Reporter:  rjollos|  Owner:  nobody
  Type:  defect | Status:  new
  Priority:  major  |  Milestone:  next 0.x
 Component:  ui design  |Version:  0.5.3
Resolution: |   Keywords:  starter qct
+-
Changes (by rjollos):

 * keywords:   => starter qct
 * owner:   => nobody
 * component:   => ui design


-- 
Ticket URL: 
Apache Bloodhound 
The Apache Bloodhound issue tracker

Re: [Apache Bloodhound] #551: Search selectors overlap with results grid

[Apache Bloodhound]

#551: Search selectors overlap with results grid
--+---
  Reporter:  olemis   |  Owner:  nobody
  Type:  defect   | Status:  new
  Priority:  trivial  |  Milestone:  next 0.x
 Component:  search   |Version:
Resolution:   |   Keywords:  grid view starter
--+---
Changes (by rjollos):

 * keywords:  grid view => grid view starter
 * milestone:   => next 0.x


-- 
Ticket URL: 
Apache Bloodhound 
The Apache Bloodhound issue tracker

Re: [Apache Bloodhound] #554: "Last Login" does not update

[Apache Bloodhound]

#554: "Last Login" does not update
--+
  Reporter:  rjollos  |  Owner:  rjollos
  Type:  defect   | Status:  accepted
  Priority:  major|  Milestone:  Unscheduled
 Component:  plugins  |Version:  0.5.3
Resolution:   |   Keywords:  AccountManager
--+
Changes (by rjollos):

 * milestone:  next 0.x => Unscheduled


-- 
Ticket URL: 
Apache Bloodhound 
The Apache Bloodhound issue tracker

Re: [Apache Bloodhound] #556: bh-demo2 site should be labeled "Latest Release"

[Apache Bloodhound]

#556: bh-demo2 site should be labeled "Latest Release"
+
  Reporter:  rjollos|  Owner:  nobody
  Type:  task   | Status:  new
  Priority:  minor  |  Milestone:
 Component:  siteadmin  |Version:
Resolution: |   Keywords:
+
Changes (by rjollos):

 * component:  projectadmin => siteadmin
 * milestone:  Unscheduled =>


-- 
Ticket URL: 
Apache Bloodhound 
The Apache Bloodhound issue tracker

Re: [Apache Bloodhound] #557: Wiki pages that were moved in the whitelabeling work should have a redirect at the old location

[Apache Bloodhound]

#557: Wiki pages that were moved in the whitelabeling work should have a 
redirect
at the old location
--+--
  Reporter:  rjollos  |  Owner:  nobody
  Type:  enhancement  | Status:  new
  Priority:  major|  Milestone:  next 0.x
 Component:  trac core|Version:
Resolution:   |   Keywords:
--+--
Changes (by rjollos):

 * component:  ui design => trac core
 * milestone:   => next 0.x


-- 
Ticket URL: 
Apache Bloodhound 
The Apache Bloodhound issue tracker

Re: [Apache Bloodhound] #550: Bootstrap template for error.html

[Apache Bloodhound]

#550: Bootstrap template for error.html
--+---
  Reporter:  rjollos  |  Owner:  nobody
  Type:  enhancement  | Status:  new
  Priority:  major|  Milestone:  next 0.x
 Component:  ui design|Version:
Resolution:   |   Keywords:  starter bootstrap
--+---
Changes (by rjollos):

 * keywords:   => starter bootstrap
 * type:  defect => enhancement
 * milestone:   => next 0.x


-- 
Ticket URL: 
Apache Bloodhound 
The Apache Bloodhound issue tracker

Re: [Apache Bloodhound] #541: TracStandalone crashing on default product misconfiguration

[Apache Bloodhound]

#541: TracStandalone crashing on default product misconfiguration
---+-
  Reporter:  olemis|  Owner:  rjollos
  Type:  defect| Status:  review
  Priority:  critical  |  Milestone:
 Component:  multiproduct  |Version:
Resolution:|   Keywords:  hooks
---+-

Comment (by rjollos):

 Is there anything left to be done for this ticket?

-- 
Ticket URL: 
Apache Bloodhound 
The Apache Bloodhound issue tracker

Re: [Apache Bloodhound] #541: TracStandalone crashing on default product misconfiguration

[Apache Bloodhound]

#541: TracStandalone crashing on default product misconfiguration
---+--
  Reporter:  olemis|  Owner:  olemis
  Type:  defect| Status:  needinfo(review)
  Priority:  critical  |  Milestone:
 Component:  multiproduct  |Version:
Resolution:|   Keywords:  hooks
---+--
Changes (by rjollos):

 * status:  review => needinfo(review)
 * owner:  rjollos => olemis


-- 
Ticket URL: 
Apache Bloodhound 
The Apache Bloodhound issue tracker