You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@bloodhound.apache.org by Apache Bloodhound <de...@bloodhound.apache.org> on 2013/05/10 18:40:28 UTC
[Apache Bloodhound] #521: Relations error on ticket page
#521: Relations error on ticket page
------------------------+---------------
Reporter: jdreimann | Owner:
Type: defect | Status: new
Priority: major | Version:
Resolution: |
------------------------+---------------
{{{!html
<div class="relations">
<div role="application">
<h3 style="display: inline;">Widget error</h3>
<br>
<div>
<p class="alert alert-error">
<span class="label label-important">
Error
</span>
Exception raised while rendering widget. Contact your
administrator for further details.
<button type="button" class="close" data-dismiss="alert">×</button>
</p>
<dl class="dl-horizontal">
<dt>Widget name</dt>
<dd>TicketRelations</dd>
<dt>Exception type</dt>
<dd><code>InvalidIdentifier</code></dd>
<dt>Log entry ID</dt>
<dd>a93d0bca-9609-494d-87df-b6d710ee2cfe</dd>
</dl>
</div>
</div>
</div>
}}}
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/521>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker
Re: [Apache Bloodhound] #521: Relations error on ticket page
Posted by Apache Bloodhound <de...@bloodhound.apache.org>.
#521: Relations error on ticket page
------------------------+----------------------
Reporter: jdreimann | Owner: matevzb
Type: defect | Status: accepted
Priority: major | Milestone:
Component: relations | Version:
Resolution: | Keywords:
------------------------+----------------------
Changes (by matevzb):
* status: new => accepted
* owner: nobody => matevzb
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/521#comment:7>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker
Re: [Apache Bloodhound] #521: Relations error on ticket page
Posted by Apache Bloodhound <de...@bloodhound.apache.org>.
#521: Relations error on ticket page
------------------------+-------------------------
Reporter: jdreimann | Owner: nobody
Type: defect | Status: new
Priority: major | Milestone:
Component: relations | Version:
Resolution: | Keywords: bhrelations
------------------------+-------------------------
Comment (by andrej):
related implementation ticket is #522
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/521#comment:5>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker
Re: [Apache Bloodhound] #521: Relations error on ticket page
Posted by Olemis Lang <ol...@gmail.com>.
On 5/11/13, Andrej Golcov <an...@digiverse.si> wrote:
[...]
>
> I suggest to make the widget including conditional, just in case if an
> admin decides to disable bhrelations plugin. Any objections on this?
>
+
... and this also covers not to attempt will be made to render it if
plugin is disabled , isn't it ?
--
Regards,
Olemis.
Re: [Apache Bloodhound] #521: Relations error on ticket page
Posted by Andrej Golcov <an...@digiverse.si>.
> Relations are a component of Bloodhound, and a "relations" component is
> already set up, so I would suggest that's the best way to distinguish
> relations tickets. You can of course use keywords in addition to that.
I was not sure that "relations" directly refers BEP-6 implementation.
Otherwise, agree:
there is no need for double reference in component and keywords.
Changed this appropriately.
Cheers, Andrej
Re: [Apache Bloodhound] #521: Relations error on ticket page
Posted by Joachim Dreimann <jo...@wandisco.com>.
On 11 May 2013 08:36, Andrej Golcov <an...@digiverse.si> wrote:
> On 10 May 2013 19:09, Joachim Dreimann <jo...@wandisco.com>
> wrote:
> > I've been trying to look into the status of the relations work and what
> is
> > left to be done, but I can't find any tickets relating to it:
> >
> https://issues.apache.org/bloodhound/query?component=relations&or&keywords=~relations&col=id&col=summary&col=owner&col=type&col=status&col=priority&col=milestone&order=priority
> >
> > I checked the BEP but again there's no indication on what progress has
> been
> > made, no indication on what is outstanding and no tickets are linked to
> > from there:
> > https://issues.apache.org/bloodhound/wiki/Proposals/BEP-0006
> I didn't feel need for tickets fro BEP-0006 during bhrelations base
> code setup, defining requirements, and discussion on the mailing list.
> But now, when the next release is close, I agree with Joachim that
> tracking of bhrelations progress is important.
> I suggest "bhrealtions" keyword for tickets if you don't mind.
>
Relations are a component of Bloodhound, and a "relations" component is
already set up, so I would suggest that's the best way to distinguish
relations tickets. You can of course use keywords in addition to that.
As for tickets, of course we don't need them for mailing list discussions.
"Code setup" seems vague in scope but I would argue that much more than
setting up has been done so far. The wider community would have benefitted
from this being codified in tickets for the reasons I mentioned above.
Once requirements are defined in the BEP, they should be broken down into
reasonably sized tickets. Being able to find / point at unambiguous tickets
defining outstanding work also lowers the barriers to entry for new
contributors.
- Joe
>
> >> I'm running into issues with it now but can't tell whether it's already
> > known, a stopgap - the issue has been around for at least a few days
> before
> > I raised it:
> > https://issues.apache.org/bloodhound/ticket/521
> As I mentioned in ticket, the problem was in moving the widget in
> bhrealtaions.* namespace that was not enabled by default. In fresh
> installation, components from bhrealtaions.* are enabled by default
> but the existing installations must be fixed manually by enabling
> bhrealtaions.* in ini file. Nigthly build demo also has to have
> bhrelations.* enabled.
>
> I suggest to make the widget including conditional, just in case if an
> admin decides to disable bhrelations plugin. Any objections on this?
> > What is happening here? This is a major feature for our issue tracker
> that
> > seems to have no representation in trackable issues.
> Bhrelations API is more or less done. Missing major parts so far are
> UI (widget on ticket page, relation management page) and notifications
> on modification. I'll setup main remaining issues and will update the
> BEP-0006 wiki page to show the list of related issues.
>
> Cheers, Andrej
--
Joe Dreimann | *User Experience Designer* | WANdisco<http://www.wandisco.com/>
@jdreimann <https://twitter.com/jdreimann>
Re: [Apache Bloodhound] #521: Relations error on ticket page
Posted by Gary Martin <ga...@wandisco.com>.
On 11/05/13 08:36, Andrej Golcov wrote:
> On 10 May 2013 19:09, Joachim Dreimann <jo...@wandisco.com> wrote:
>> I've been trying to look into the status of the relations work and what is
>> left to be done, but I can't find any tickets relating to it:
>> https://issues.apache.org/bloodhound/query?component=relations&or&keywords=~relations&col=id&col=summary&col=owner&col=type&col=status&col=priority&col=milestone&order=priority
>>
>> I checked the BEP but again there's no indication on what progress has been
>> made, no indication on what is outstanding and no tickets are linked to
>> from there:
>> https://issues.apache.org/bloodhound/wiki/Proposals/BEP-0006
> I didn't feel need for tickets fro BEP-0006 during bhrelations base
> code setup, defining requirements, and discussion on the mailing list.
> But now, when the next release is close, I agree with Joachim that
> tracking of bhrelations progress is important.
> I suggest "bhrealtions" keyword for tickets if you don't mind.
I have no particular problem with that if you find it makes life easier
for you but I tend to think that the relations component would be enough
to characterise the work. I hope you excuse me when I rarely set
keywords on any of the tickets that I raise!
>
>>> I'm running into issues with it now but can't tell whether it's already
>> known, a stopgap - the issue has been around for at least a few days before
>> I raised it:
>> https://issues.apache.org/bloodhound/ticket/521
> As I mentioned in ticket, the problem was in moving the widget in
> bhrealtaions.* namespace that was not enabled by default. In fresh
> installation, components from bhrealtaions.* are enabled by default
> but the existing installations must be fixed manually by enabling
> bhrealtaions.* in ini file. Nigthly build demo also has to have
> bhrelations.* enabled.
We could look at enabling bhrelations as a part of the upgrade to 0.6.0
if we believe that it is ready at that point.
> I suggest to make the widget including conditional, just in case if an
> admin decides to disable bhrelations plugin. Any objections on this?
That makes good sense I think.
Cheers,
Gary
Re: [Apache Bloodhound] #521: Relations error on ticket page
Posted by Andrej Golcov <an...@digiverse.si>.
On 10 May 2013 19:09, Joachim Dreimann <jo...@wandisco.com> wrote:
> I've been trying to look into the status of the relations work and what is
> left to be done, but I can't find any tickets relating to it:
> https://issues.apache.org/bloodhound/query?component=relations&or&keywords=~relations&col=id&col=summary&col=owner&col=type&col=status&col=priority&col=milestone&order=priority
>
> I checked the BEP but again there's no indication on what progress has been
> made, no indication on what is outstanding and no tickets are linked to
> from there:
> https://issues.apache.org/bloodhound/wiki/Proposals/BEP-0006
I didn't feel need for tickets fro BEP-0006 during bhrelations base
code setup, defining requirements, and discussion on the mailing list.
But now, when the next release is close, I agree with Joachim that
tracking of bhrelations progress is important.
I suggest "bhrealtions" keyword for tickets if you don't mind.
>> I'm running into issues with it now but can't tell whether it's already
> known, a stopgap - the issue has been around for at least a few days before
> I raised it:
> https://issues.apache.org/bloodhound/ticket/521
As I mentioned in ticket, the problem was in moving the widget in
bhrealtaions.* namespace that was not enabled by default. In fresh
installation, components from bhrealtaions.* are enabled by default
but the existing installations must be fixed manually by enabling
bhrealtaions.* in ini file. Nigthly build demo also has to have
bhrelations.* enabled.
I suggest to make the widget including conditional, just in case if an
admin decides to disable bhrelations plugin. Any objections on this?
> What is happening here? This is a major feature for our issue tracker that
> seems to have no representation in trackable issues.
Bhrelations API is more or less done. Missing major parts so far are
UI (widget on ticket page, relation management page) and notifications
on modification. I'll setup main remaining issues and will update the
BEP-0006 wiki page to show the list of related issues.
Cheers, Andrej
Re: [Apache Bloodhound] #521: Relations error on ticket page
Posted by Olemis Lang <ol...@gmail.com>.
On 5/10/13, Joachim Dreimann <jo...@wandisco.com> wrote:
>
[...]
>
> I'm running into issues with it now but can't tell whether it's already
> known, a stopgap - the issue has been around for at least a few days before
> I raised it:
> https://issues.apache.org/bloodhound/ticket/521
>
Is BH Relations widget component actually enabled at bh-demo1.a.o ?
[...]
--
Regards,
Olemis.
Re: [Apache Bloodhound] #521: Relations error on ticket page
Posted by Joachim Dreimann <jo...@wandisco.com>.
I've been trying to look into the status of the relations work and what is
left to be done, but I can't find any tickets relating to it:
https://issues.apache.org/bloodhound/query?component=relations&or&keywords=~relations&col=id&col=summary&col=owner&col=type&col=status&col=priority&col=milestone&order=priority
I checked the BEP but again there's no indication on what progress has been
made, no indication on what is outstanding and no tickets are linked to
from there:
https://issues.apache.org/bloodhound/wiki/Proposals/BEP-0006
..unlike BEP-0003 (Multiproduct) which has a helpful ticket summary table:
https://issues.apache.org/bloodhound/wiki/Proposals/BEP-0003
I'm running into issues with it now but can't tell whether it's already
known, a stopgap - the issue has been around for at least a few days before
I raised it:
https://issues.apache.org/bloodhound/ticket/521
What is happening here? This is a major feature for our issue tracker that
seems to have no representation in trackable issues.
On 10 May 2013 17:45, Apache Bloodhound <de...@bloodhound.apache.org> wrote:
> #521: Relations error on ticket page
> ------------------------+--------------------
> Reporter: jdreimann | Owner: nobody
> Type: defect | Status: new
> Priority: major | Milestone:
> Component: relations | Version:
> Resolution: | Keywords:
> ------------------------+--------------------
> Changes (by jdreimann):
>
> * component: dashboard => relations
>
>
> Old description:
>
> > {{{
> > #!html
> > <div class="relations">
> > <div role="application">
> > <h3 style="display: inline;">Widget error</h3>
> >
> > <br>
> > <div>
> > <p class="alert alert-error">
> > <span class="label label-important">
> > Error
> > </span>
> > Exception raised while rendering widget. Contact your
> > administrator for further details.
> > <button type="button" class="close" data-dismiss="alert">×</button>
> > </p>
> > <dl class="dl-horizontal">
> > <dt>Widget name</dt>
> > <dd>TicketRelations</dd>
> > <dt>Exception type</dt>
> > <dd><code>InvalidIdentifier</code></dd>
> > <dt>Log entry ID</dt>
> > <dd>a93d0bca-9609-494d-87df-b6d710ee2cfe</dd>
> > </dl>
> > </div>
> > </div>
> > </div>
> > }}}
>
> New description:
>
> I'm encountering the following error on every ticket page:
>
> {{{
> #!html
> <div class="relations">
> <div role="application">
> <h3 style="display: inline;">Widget error</h3>
>
> <br>
> <div>
> <p class="alert alert-error">
> <span class="label label-important">
> Error
> </span>
> Exception raised while rendering widget. Contact your
> administrator for further details.
> <button type="button" class="close" data-dismiss="alert">×</button>
> </p>
> <dl class="dl-horizontal">
> <dt>Widget name</dt>
> <dd>TicketRelations</dd>
> <dt>Exception type</dt>
> <dd><code>InvalidIdentifier</code></dd>
> <dt>Log entry ID</dt>
> <dd>a93d0bca-9609-494d-87df-b6d710ee2cfe</dd>
> </dl>
> </div>
> </div>
> </div>
> }}}
>
> I installed Bloodhound prior to r1480991, but have updated the
> installation to the latest (r1481082), not sure if that makes a
> difference. Our nightly bh-demo1 is also [https://bh-
> demo1.apache.org/products/%40/ticket/513 suffering from this] (today at
> least).
>
> --
>
> --
> Ticket URL: <https://issues.apache.org/bloodhound/ticket/521#comment:2>
> Apache Bloodhound <https://issues.apache.org/bloodhound/>
> The Apache Bloodhound issue tracker
>
--
Joe Dreimann | *User Experience Designer* | WANdisco<http://www.wandisco.com/>
@jdreimann <https://twitter.com/jdreimann>
*
*
*Join one of our free daily demo sessions on* *Scaling Subversion for the
Enterprise <http://www.wandisco.com/training/webinars>*
THIS MESSAGE AND ANY ATTACHMENTS ARE CONFIDENTIAL, PROPRIETARY, AND MAY BE
PRIVILEGED. If this message was misdirected, WANdisco, Inc. and its
subsidiaries, ("WANdisco") does not waive any confidentiality or privilege.
If you are not the intended recipient, please notify us immediately and
destroy the message without disclosing its contents to anyone. Any
distribution, use or copying of this e-mail or the information it contains
by other than an intended recipient is unauthorized. The views and
opinions expressed in this e-mail message are the author's own and may not
reflect the views and opinions of WANdisco, unless the author is authorized
by WANdisco to express such views or opinions on its behalf. All email
sent to or from this address is subject to electronic storage and review by
WANdisco. Although WANdisco operates anti-virus programs, it does not
accept responsibility for any damage whatsoever caused by viruses being
passed.
Re: [Apache Bloodhound] #521: Relations error on ticket page
Posted by Apache Bloodhound <de...@bloodhound.apache.org>.
#521: Relations error on ticket page
------------------------+--------------------
Reporter: jdreimann | Owner: nobody
Type: defect | Status: new
Priority: major | Milestone:
Component: relations | Version:
Resolution: | Keywords:
------------------------+--------------------
Changes (by jdreimann):
* component: dashboard => relations
Old description:
> {{{
> #!html
> <div class="relations">
> <div role="application">
> <h3 style="display: inline;">Widget error</h3>
>
> <br>
> <div>
> <p class="alert alert-error">
> <span class="label label-important">
> Error
> </span>
> Exception raised while rendering widget. Contact your
> administrator for further details.
> <button type="button" class="close" data-dismiss="alert">×</button>
> </p>
> <dl class="dl-horizontal">
> <dt>Widget name</dt>
> <dd>TicketRelations</dd>
> <dt>Exception type</dt>
> <dd><code>InvalidIdentifier</code></dd>
> <dt>Log entry ID</dt>
> <dd>a93d0bca-9609-494d-87df-b6d710ee2cfe</dd>
> </dl>
> </div>
> </div>
> </div>
> }}}
New description:
I'm encountering the following error on every ticket page:
{{{
#!html
<div class="relations">
<div role="application">
<h3 style="display: inline;">Widget error</h3>
<br>
<div>
<p class="alert alert-error">
<span class="label label-important">
Error
</span>
Exception raised while rendering widget. Contact your
administrator for further details.
<button type="button" class="close" data-dismiss="alert">×</button>
</p>
<dl class="dl-horizontal">
<dt>Widget name</dt>
<dd>TicketRelations</dd>
<dt>Exception type</dt>
<dd><code>InvalidIdentifier</code></dd>
<dt>Log entry ID</dt>
<dd>a93d0bca-9609-494d-87df-b6d710ee2cfe</dd>
</dl>
</div>
</div>
</div>
}}}
I installed Bloodhound prior to r1480991, but have updated the
installation to the latest (r1481082), not sure if that makes a
difference. Our nightly bh-demo1 is also [https://bh-
demo1.apache.org/products/%40/ticket/513 suffering from this] (today at
least).
--
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/521#comment:2>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker
Re: [Apache Bloodhound] #521: Relations error on ticket page
Posted by Apache Bloodhound <de...@bloodhound.apache.org>.
#521: Relations error on ticket page
------------------------+-------------------------
Reporter: jdreimann | Owner: nobody
Type: defect | Status: new
Priority: major | Milestone:
Component: relations | Version:
Resolution: | Keywords: bhrelations
------------------------+-------------------------
Changes (by andrej):
* keywords: => bhrelations
Comment:
bhrelation widget was moved from bhdashboard.* to bhrelations.* namespace.
bhrelations.* components must be enabled in ini file in order to make the
widget active.
Currently, fresh installations have bhrelations.* components enabled by
default. For existing installations, bhrelations.* components should be
enabled in ini file manually.
I suggest changing the ticket page to include bhrelation widget
conditionally, only if the widget is enabled.
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/521#comment:4>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker
Re: [Apache Bloodhound] #521: Relations error on ticket page
Posted by Apache Bloodhound <de...@bloodhound.apache.org>.
#521: Relations error on ticket page
------------------------+--------------------
Reporter: jdreimann | Owner: nobody
Type: defect | Status: new
Priority: major | Milestone:
Component: dashboard | Version:
Resolution: | Keywords:
------------------------+--------------------
Changes (by jdreimann):
* owner: => nobody
* component: => dashboard
Old description:
> {{{!html
> <div class="relations">
> <div role="application">
> <h3 style="display: inline;">Widget error</h3>
>
> <br>
> <div>
> <p class="alert alert-error">
> <span class="label label-important">
> Error
> </span>
> Exception raised while rendering widget. Contact your
> administrator for further details.
> <button type="button" class="close" data-dismiss="alert">×</button>
> </p>
> <dl class="dl-horizontal">
> <dt>Widget name</dt>
> <dd>TicketRelations</dd>
> <dt>Exception type</dt>
> <dd><code>InvalidIdentifier</code></dd>
> <dt>Log entry ID</dt>
> <dd>a93d0bca-9609-494d-87df-b6d710ee2cfe</dd>
> </dl>
> </div>
> </div>
> </div>
> }}}
New description:
{{{
#!html
<div class="relations">
<div role="application">
<h3 style="display: inline;">Widget error</h3>
<br>
<div>
<p class="alert alert-error">
<span class="label label-important">
Error
</span>
Exception raised while rendering widget. Contact your
administrator for further details.
<button type="button" class="close" data-dismiss="alert">×</button>
</p>
<dl class="dl-horizontal">
<dt>Widget name</dt>
<dd>TicketRelations</dd>
<dt>Exception type</dt>
<dd><code>InvalidIdentifier</code></dd>
<dt>Log entry ID</dt>
<dd>a93d0bca-9609-494d-87df-b6d710ee2cfe</dd>
</dl>
</div>
</div>
</div>
}}}
--
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/521#comment:1>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker
Re: [Apache Bloodhound] #521: Relations error on ticket page
Posted by Apache Bloodhound <de...@bloodhound.apache.org>.
#521: Relations error on ticket page
------------------------+-----------------------
Reporter: jdreimann | Owner: jdreimann
Type: defect | Status: closed
Priority: major | Milestone:
Component: relations | Version:
Resolution: fixed | Keywords:
------------------------+-----------------------
Changes (by astaric):
* status: review => closed
* resolution: => fixed
Comment:
The error no longer appears on current trunk version of bloodhound, even
with bhrelations module disabled.
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/521#comment:9>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker
Re: [Apache Bloodhound] #521: Relations error on ticket page
Posted by Apache Bloodhound <de...@bloodhound.apache.org>.
#521: Relations error on ticket page
------------------------+--------------------
Reporter: jdreimann | Owner: nobody
Type: defect | Status: new
Priority: major | Milestone:
Component: relations | Version:
Resolution: | Keywords:
------------------------+--------------------
Comment (by olemis):
Replying to [ticket:521 jdreimann]:
> I'm encountering the following error on every ticket page:
>
> {{{
> #!html
> <div class="relations">
> <div role="application">
> <h3 style="display: inline;">Widget error</h3>
>
> <br>
> <div>
> <p class="alert alert-error">
> <span class="label label-important">
> Error
> </span>
> Exception raised while rendering widget. Contact your
administrator for further details.
> <button type="button" class="close" data-dismiss="alert">×</button>
> </p>
> <dl class="dl-horizontal">
> <dt>Widget name</dt>
> <dd>TicketRelations</dd>
> <dt>Exception type</dt>
> <dd><code>InvalidIdentifier</code></dd>
> <dt>Log entry ID</dt>
> <dd>a93d0bca-9609-494d-87df-b6d710ee2cfe</dd>
> </dl>
> </div>
> </div>
> </div>
> }}}
>
[...]
@jdreimann : This error report will be more useful after posting related
entries in the log file . After enabling TracLogging , please search for
entry ID in log records (e.g. `a93d0bca-9609-494d-87df-b6d710ee2cfe`) and
provide further details about this failure mode in order to determine
what's going wrong with this .
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/521#comment:3>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker
Re: [Apache Bloodhound] #521: Relations error on ticket page
Posted by Apache Bloodhound <de...@bloodhound.apache.org>.
#521: Relations error on ticket page
------------------------+-----------------------
Reporter: jdreimann | Owner: jdreimann
Type: defect | Status: closed
Priority: major | Milestone: Release 6
Component: relations | Version:
Resolution: fixed | Keywords:
------------------------+-----------------------
Changes (by rjollos):
* milestone: => Release 6
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/521#comment:10>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker
Re: [Apache Bloodhound] #521: Relations error on ticket page
Posted by Apache Bloodhound <de...@bloodhound.apache.org>.
#521: Relations error on ticket page
------------------------+-----------------------
Reporter: jdreimann | Owner: jdreimann
Type: defect | Status: review
Priority: major | Milestone:
Component: relations | Version:
Resolution: | Keywords:
------------------------+-----------------------
Changes (by matevzb):
* owner: matevzb => jdreimann
* status: accepted => review
Comment:
The relations widget is now displayed only if bhrelations component is
enabled, please check against r1482233.
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/521#comment:8>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker
Re: [Apache Bloodhound] #521: Relations error on ticket page
Posted by Apache Bloodhound <de...@bloodhound.apache.org>.
#521: Relations error on ticket page
------------------------+--------------------
Reporter: jdreimann | Owner: nobody
Type: defect | Status: new
Priority: major | Milestone:
Component: relations | Version:
Resolution: | Keywords:
------------------------+--------------------
Changes (by andrej):
* keywords: bhrelations =>
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/521#comment:6>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker