toddfarmer commented on issue #14507: URL: https://github.com/apache/arrow/issues/14507#issuecomment-1292138626
To me, this issue focuses on defining what we want to retain of the ASF Jira issue type field. As you rightly note, retaining references across Jira issues has significant additional value, and I've opened #14520 to track that independently. I still think there's value in knowing the issue type of an issue migrated from ASF Jira. If not "sub-task" as a label, should we not include an explicit type label? Should we call it a "task", effectively elevating it from sub-task to task? I agree that the notion of a "sub-task" label is unlikely to be consistently applied in future manually-created GitHub issues, though it may be possible with issue templates and forms (e.g., a special form to create a sub-task of an existing issue which properly sets the label and requires a reference to the parent issue). -- 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]
