toddfarmer commented on issue #14520: URL: https://github.com/apache/arrow/issues/14520#issuecomment-1311118773
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 three reasons. First, only a select number of people can update the description to modify the related issues list. These individuals may not include an assignee. Second, the related issues are unstructured. Yes, we can propose standard formatting as has been described above, but ... there's no guarantee that people will follow it, and any slight deviation will make it difficult to extract related issues for any sort of reporting. Third, it's virtually impossible to filter on that content. Yes, the target related issue will have a back-link, but this [persist even after it is removed from the source issue](https://github.com/toddfarmer/test_import/issues/95), meaning there will be false positive back-links. ### Adding associated issues in comments This has the same problem, but it adds the additional challenge that the related issues are disbursed across any number of issue comments. It allows different users to add new related issue links, partially mitigating the first problem above, but does not solve the problem of removing links to issues that are no longer considered related. Again, only a select group of individuals can modify comments made by a given user. ### Using a related issue project This is demonstrated in [this issue](https://github.com/toddfarmer/test-arrow-config/issues/17):  Projects allow for custom fields to be defined and used, and in this example, child issues can be associated with a parent issue. The management of this isn't easy - every new parent issue requires adding a value to the custom field picklist, and adding an issue to a project can also only be done by a limited number of people. However, these operations could be automated with GitHub actions. While the custom fields in a project cannot be used in normal issue filtering, projects themselves have search and dashboard capabilities that can use these fields to filter:  -- 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]
