> Is it intentional that we do not set Assignees on migration? You can assign a GitHub account only when it has push access to the repository; it was infeasible to give push access to all committers to the test repo (an invite/accept flow is needed for each committer). Assignees will be set when the actual migration on apache/lucene repo - every assignee in Jira should have push access to it.
Tomoko 2022年7月31日(日) 8:16 Michael McCandless <luc...@mikemccandless.com>: > Is it intentional that we do not set Assignees on migration? > > E.g. this issue ( > https://github.com/mocobeta/forks-migration-test/issues/5916) is assigned > to Ryan in Jira, but has no Assignees in GitHub issue. > > Mike > > On Sat, Jul 30, 2022 at 6:40 PM Michael McCandless < > luc...@mikemccandless.com> wrote: > >> On Sat, Jul 30, 2022 at 6:29 PM Michael McCandless < >> luc...@mikemccandless.com> wrote: >> >> How about hidden (secure) issues? I assume they did not migrate as >>> well? Do GitHub issues offer such hidden/secure issues? >>> >> >> OK nevermind -- Tomoko already raised this question here on June 15 and >> the conclusion was that Lucene never enabled such private issues (Solr >> did), so there is nothing to do/see here! >> >> Mike >> -- >> Mike McCandless >> >> http://blog.mikemccandless.com >> > -- > Mike McCandless > > http://blog.mikemccandless.com >
