#434: Ticket query macro in product context - after #390
---------------------------+----------------------------------------------
Reporter: olemis | Owner: nobody
Type: defect | Status: new
Priority: blocker | Milestone:
Component: multiproduct | Version:
Resolution: | Keywords: ticket query product db bep-0003
---------------------------+----------------------------------------------
Changes (by olemis):
* keywords: ticket query product db => ticket query product db bep-0003
Old description:
> Test cases written for #390 detected that TicketQuery macro is not
> working neither in product nor global scope. See
> [http://pastebin.com/PSzv0eZd this test report] for further details .
>
> {{{
> #!span class="label label-info"
>
> Update
> }}} TicketQueryMacro has to be upgraded to support multi-product
> environments .
>
> Besides afaict the way it stand now it will be impossible to make queries
> for tickets in another product due to the fact that the underlying DB
> connection will always be translated and thereby `product=PREFIX`
> constraint will be silently implicit .
New description:
Test cases written for #390 detected that TicketQuery macro is not working
neither in product nor global scope. See [http://pastebin.com/PSzv0eZd
this test report] for further details .
{{{
#!span class="label label-info"
Update
}}}
`TicketQueryMacro` has to be upgraded to support multi-product
environments .
Besides afaict the way it stand now it will be impossible to make queries
for tickets in another product due to the fact that the underlying DB
connection will always be translated and thereby `product=PREFIX`
constraint will be silently implicit .
--
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/434#comment:4>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker
