toddfarmer opened a new issue, #14510: URL: https://github.com/apache/arrow/issues/14510
In anticipation of a potential migration from ASF Jira to GitHub for issue tracking, an assessment is needed on whether we can and should map user accounts in migrated content. GitHub and ASF Jira use different user identifiers, which often differ (or collide with unrelated users) across systems. This has implications for: * Issue reporter * Issue assignee * Watchers * Comment authors * User mentions Issue assignee could be retained if we have a mapping table to convert Jira user accounts to corresponding GitHub user accounts for individuals. This could be "best effort", and fall back to simply recording the Jira user name and display name in a comment if no mapping is supplied. Issue reporter cannot be set using the [GitHub issue import API](https://gist.github.com/jonmagic/5282384165e0f86ef105), so I plan to record the reporter displayName and username in a prefix to the issue description (see [example here](https://github.com/toddfarmer/test_import/issues/18). Watchers cannot be set via the import API. We may be able to supply a simple script for interested users to execute that would set themselves as a watcher on GitHub issues that were migrated from Jira issues they were watching. Comment authors cannot be set via the import API. I've prefixed the issue comment with the original reporter displayname and username, and a link back to the original Jira comment. User mentions can be mapped as part of content mapping. If there is no user account mapping, this could fall back to using the ASF Jira username in a code block (e.g., `[~toddfarmer]`). -- 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]
