[
https://issues.apache.org/jira/browse/ARROW-18377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17655535#comment-17655535
]
Rok Mihevc commented on ARROW-18377:
------------------------------------
[~raulcd] [~assignUser] this would indeed be nice to have. I can also back fill
the labels via the API once this is in place.
> MIGRATION: Automate component labels from issue form content
> ------------------------------------------------------------
>
> Key: ARROW-18377
> URL: https://issues.apache.org/jira/browse/ARROW-18377
> Project: Apache Arrow
> Issue Type: Task
> Reporter: Todd Farmer
> Priority: Major
> Labels: gh-migration
>
> ARROW-18364 added the ability to report issues in GitHub, and includes GitHub
> issue templates with a drop-down component(s) selector. These form elements
> drive resulting issue markdown only, and cannot dynamically drive issue
> labels. This requires GitHub actions, which also have a few limitations.
> First, the issue form does not produce any structured data, it only produces
> the issue description markdown, so a parser is required. Second, ASF
> restricts GitHub actions to a selection of approved actions. It is likely
> that while community actions exist to generate structured data from issue
> forms, the Apache Arrow project will need to write its own parser and label
> application action.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
