jorisvandenbossche commented on issue #14520: URL: https://github.com/apache/arrow/issues/14520#issuecomment-1311393676
> First, only a select number of people can update the description to modify the related issues list. These individuals may not include an assignee. I am not sure this will be a problem in practice: 1) we can give triage rights to regular contributors that are not committers (we just haven't been doing that now, because we didn't need that for JIRA, 2) in most cases it is the person who opened the issue who that will create a list of subtasks, in which case they can edit it anyway (this is probably not true for migrated issues, since they don't become the author of that issue? But also here, we still have item 1)) So personally my guess is that this will be OK in practice, and it is still something we can address later and try to find a different solution (or helper bots) if it turns out to give problems. I would say that using task lists for the subtask relation on JIRA is, despite its limitations, by far the easiest. I think we could explore using GitHub Project features, but that feels something we should experiment with while using it, and something we can start to use later. I personally wouldn't already use this for the migration. -- 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]
