[
https://issues.apache.org/jira/browse/ARROW-18381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17637624#comment-17637624
]
Antoine Pitrou commented on ARROW-18381:
----------------------------------------
bq. This means that 314 legacy issues will lose metadata associating with at
least one version that it was associated with in Jira. Is this acceptable?
Should the lowest or highest associated Jira version be used during import, if
so?
bq.
Well, it can't be avoided, so I guess we'll have to accept it :-)
As for which version should be used, I would say the lowest version - which is
generally a bugfix version released earlier than the following feature version.
cc [~kou] for advice.
> MIGRATION: Create milestones for every needed fix version
> ---------------------------------------------------------
>
> Key: ARROW-18381
> URL: https://issues.apache.org/jira/browse/ARROW-18381
> Project: Apache Arrow
> Issue Type: Task
> Reporter: Todd Farmer
> Priority: Major
> Attachments: Screenshot from 2022-11-22 11-53-07.png, Screenshot from
> 2022-11-22 11-54-26.png
>
>
> The Apache Arrow projects uses the "Fix version" field in ASF Jira issue to
> track the version in which issues were resolved/fixed/implemented. The most
> equivalent field in GitHub issues is the "milestone" field. This field is
> explicitly managed - the versions need to be added to the repository
> configuration before they can be used. This mapping needs to be established
> as a prerequisite for completing the import from ASF Jira.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
