As one of those affected, what should I do? I already created a new account as zamsden, but all of my issues are assigned to zamsden_impala_ad21. Should I reassign and transfer things over or am I forever doomed to be zamsden_impala_ad21?
Thanks, - Zach On Mon, Mar 13, 2017 at 2:24 PM, Jim Apple <jbap...@cloudera.com> 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 d...@impala.apache.org. > > 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. >
