mikemccand commented on issue #37: URL: https://github.com/apache/lucene-jira-archive/issues/37#issuecomment-1188840453
> So to detect "moved" issues, just compare returned key with requested key. I remembered that I had the same challenge with [jirasearch](https://jirasearch.mikemccandless.com)! [This](https://github.com/mikemccand/luceneserver/blob/master/examples/jirasearch/indexJira.py#L272-L290) is how I solved it. You must iterate the issue history looking for an update to the `Key` field, I think? But @uschindler's solution is even simpler! I should fix the jirasearch impl :) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
