uschindler commented on issue #37: URL: https://github.com/apache/lucene-jira-archive/issues/37#issuecomment-1188834761
> This reminds me that we should exclude the moved issues (to Solr or possibly another project) from migration, but can't figure out ways to detect "moved" issues... Jira API returns data for already moved issues such as https://issues.apache.org/jira/browse/LUCENE-4344, but not sure if there is a field to decide whether it has been moved or not. (T⌓T) I don't know which JIRA API you use. But when you use the offiial "get issue" API to read all information, it is easy to detect; look at the API respose: https://issues.apache.org/jira/rest/api/2/issue/LUCENE-4344 The root object has the "key" of issue. In this case we requested LUCENE-4344, but the JSON response has `{"key": "SOLR-3769",....}` in the response. The key in the JSON is always the canonic issue number. It may also happen that you have a "redirect" to another LUCENE issue number (if somebody moved the issue to solr and then decided to move it back to Lucene). So to detect "moved" issues, just compare returned key with requested key. -- 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
