toddfarmer commented on issue #14510: URL: https://github.com/apache/arrow/issues/14510#issuecomment-1297705902
My current belief is that we cannot effectively migrate issue watchers/subscriptions from Jira to GitHub issues, and that it may be necessary to create a simple Python script for individuals to execute post-migration that will: 1. Query Jira to find existing issues they are subscribed to 2. Obtain the migrated GitHub issue identifier from a designated field in the Jira issue 3. Subscribe them to the migrated GitHub issue The above seems something we can reasonable automate in a simple script, along with documentation on how to set up necessary auth to successfully execute it. But it seems we can't directly import the watchers, even if we can map user identifiers. Unless I'm missing it, the only possible viable alternative that retains issue subscriptions would be to [perform an OAuth impersonation dance](https://developer.github.com/enterprise/2.3/v3/users/administration/#create-an-impersonation-oauth-token) for every needed user/subscription - and as was noted in the links @jorisvandenbossche cited above, that seems to only be available for GitHub Enterprise customers (seems unlikely that applies to us). -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
