#792: Invalid search result after moving ticket to another product
-----------------------+------------------------------------------
Reporter: olemis | Owner: nobody
Type: defect | Status: new
Priority: critical | Milestone: next 0.x
Component: search | Version: 0.8.0dev
Resolution: | Keywords: ticket batch modify, product
-----------------------+------------------------------------------
Comment (by olemis):
Replying to [comment:3 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.
>
ok , thanks for trying thid out .
> Is the ability to move tickets through the Batch Modify form a feature
that was intentionally implemented?
Indeed it was intentional and mentioned as a last recourse approach in
other conversations [citation needed].
> We don't allow the product to be changed from the ticket form,
No ... even if we should ...
> and I wonder if we have really implemented support to move tickets,
If we haven't then we should do it rather than removing this feature from
batch modify form .
> or if instead it just sort of works by chance.
In our deployments moving tickets onto another product just works . The
issue I've detected is related to free text search only . Everything else
just works . I guess this is due to (e.g. an exception thrown while
executing) the underlying whoosh indexing strategy ? I could not find
anything in the logs though .
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/792#comment:5>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker
