I expect such redirection to be a little difficult to configure. But it seems like the same (or similar) JQL should work on issues.apache.org For example:
https://issues.apache.org/jira/issues/?jql=type%20%3D%20bug%20and%20project%20%3D%20IMPALA%20AND%20resolution%20%3D%20fixed%20AND%20affectedVersion%20!%3D%20%22Impala%202.8.0%22%20AND%20fixVersion%20%3D%20%22Impala%202.8.0%22%20and%20not%20labels%20%3D%20broken-build%20order%20by%20priority%20desc On Tue, Mar 21, 2017 at 12:47 PM, John Russell <[email protected]> wrote: > Just confirming: if I have a JIRA report URL, for example > > https://issues.cloudera.org/issues/?jql=type%20%3D%20bug% > 20and%20project%20%3D%20IMPALA%20AND%20resolution%20%3D%20fixed%20AND% > 20affectedVersion%20!%3D%20%22Impala%202.8.0%22%20AND% > 20fixVersion%20%3D%20%22Impala%202.8.0%22%20and% > 20not%20labels%20%3D%20broken-build%20order%20by%20priority%20desc > > should I expect that to redirect over to issues.apache.org also? > Currently such a report stays on issues.cloudera.org. > > There are a bunch of such report links in the Impala release notes. > > Thanks, > John > > > On Mar 13, 2017, at 2:24 PM, Jim Apple <[email protected]> wrote: > > > > If you read or write Impala JIRAs, this message is for you. > > > > Impala's JIRA is now at https://issues.apache.org/jira/browse/IMPALA/. > Links like https://issues.cloudera.org/browse/IMPALA-3224 should now > redirect to https://issues.apache.org/jira/browse/IMPALA-3224. > > > > Permissions on the Apache JIRA are much more strict. We have tried to > make them almost as permissive for the IMPALA project as they were on the > IMPALA project on issues.cloudera.org. If you need permissions you don't > have, please email [email protected]. > > > > Other than that, we don't know of any major issues at this point, > however we have found and fixed some unexpected problems so far, and others > may exist. If you find something that is impeding your work, please file a > subtask of https://issues.apache.org/jira/browse/IMPALA-5064. > > > > We tried to translate usernames as accurately as possible. In many cases > this worked just fine. In some cases this was not possible, and you will > see the issues that you participated on as $OLDUSERNAME now list you as > $OLDUSERNAME_impala_1de3, with some random-looking hex digits after your > name. You can claim that username by resetting your password: > > > > 1. Go to https://issues.apache.org/jira/secure/ForgotLoginDetails.jspa > > 2. Forgot Password, enter the username that looks like > $OLDUSERNAME_impala_1ead > > 3. Wait for email > > 4. Reset password > > > > If you have problems with that process, please follow > https://www.apache.org/dev/infra-contact and contact Apache > infrastructure. The Impala community does not administer the JIRA server. > >
