jorisvandenbossche commented on issue #14520: URL: https://github.com/apache/arrow/issues/14520#issuecomment-1313841542
That example looks good to me! > 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 are [added in comments](https://github.com/toddfarmer/test-arrow-config/issues/23). I think that is fine. We also only want to use task lists in the main issue description I think, not spread across comments (for the purpose of having a "parent" issue with sub tasks) > 2\. The "tracked in" does get updated when [sub-tasks get removed](https://github.com/toddfarmer/test-arrow-config/issues/21), though the activity stream in the previously-referenced issue still cites the (no-longer) referencing parent issue.. I think that is also fine. The issue _was_ referenced at some point by the parent, so this information can still be useful when reading that issue, even thought it might no longer be an "official" sub task. > 3\. The syntax required to track issues as sub-tasks adds a checkbox, which only partially syncs to the referenced issue status. [This issue](https://github.com/toddfarmer/test-arrow-config/issues/23) shows an unchecked box for the completed sub-task, because I closed the sub-task first, then created the parent issue without explicitly adding the "X" to the checkbox. I would find this only a minor issue, that can easily be corrected by the people actively working on an issue with subtasks (it's easy to quickly mark one as completed if you see a mismatch like this. In fact, if you make manual task lists that include more text than just the issue number, you actually always have to do this manually, as github then won't automatically tick the box). 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 JIRA/issue is open or closed?) -- 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]
