#792: Invalid search result after moving ticket to another product
-----------------------+------------------------------------------
Reporter: olemis | Owner: nobody
Type: defect | Status: new
Priority: critical | Milestone:
Component: search | Version: 0.8.0dev
Resolution: | Keywords: ticket batch modify, product
-----------------------+------------------------------------------
Comment (by rjollos):
I've tried reproducing the behavior a few times with SQLite. The result I
see is that search returns the ticket in `P1` but not `P2`. Following the
link to the ticket results in //Ticket N does not exist.// I'll need to do
more testing to see if the result is different in PostgreSQL.
Is the ability to move tickets through the Batch Modify form a feature
that was intentionally implemented? We don't allow the product to be
changed from the ticket form, and I wonder if we have really implemented
support to move tickets, or if instead it just sort of works by chance.
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/792#comment:3>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker
