Todd Farmer

#14648 tracks a problem encountered during a dry run where GitHub rejects importing certain issues with very large comments (possibly also very large descriptions).

@jorisvandenbossche: > Links to pull requests don't yet seem to be included? This is correct. I've opened #14710 to address this. Please comment there on requirements (e.g., would a comment...

> Can we also try to migrate the JIRA labels `good-first-issue` and `good-second-issue`? They are useful to mark issues suitable for fledgling contributors. Good suggestion! I've created https://github.com/apache/arrow/issues/14724 to track...

I'm finding associating issues to be the most challenging problem of the proposed migration. There are a few options: ### Listing associated issues in issue description This is problematic for...

@jorisvandenbossche : I see what you're saying now, thanks. Some observations: 1. The "tracked in" only gets managed when the sub-tasks are [listed in the issue description](https://github.com/toddfarmer/test-arrow-config/issues/22), not when they...

FYI, I've implemented the post-import update to the migrated issue description to add a list of sub-tasks to the parent issue. See [this example](https://github.com/toddfarmer/test_import/issues/268) - but ignore the rest of...

Yes, my plan is to add all formally related issue links - those where a link has been added, rather than simply mentioned inline in an issue comment - to...

[This sample issue](https://github.com/toddfarmer/test_import/issues/304) provides an example of the related (non-subtask) issue handling I propose.

> But maybe this could even be fixed in the script that adds the subtasks in a second step? (as I suppose it is known at that point if the...

The logic has been updated as follows: ``` if issue_type in ["Bug"]: return "Type: bug" if issue_type in ["Improvement", "Wish", "New Feature"]: return "Type: enhancement" if issue_type in ["Task", "Sub-task"]:...