infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Wes McKinney (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (INFRA-18041) Redundant JIRA link types
Date Tue, 19 Mar 2019 13:41:00 GMT

    [ https://issues.apache.org/jira/browse/INFRA-18041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16796086#comment-16796086
] 

Wes McKinney commented on INFRA-18041:
--------------------------------------

Hm, this one is tough. The ASF JIRA has on the order of 1 million issues across hundreds of
projects. To my native-English-speaking ears, "supersedes" and "duplicates" have different
connotations, and may have meaning for the developers of one project but not for another.


On the other hand "contained by" and "is part of" might be worth merging. Since this affects
many projects, more opinions would have to be solicited. 

> Redundant JIRA link types
> -------------------------
>
>                 Key: INFRA-18041
>                 URL: https://issues.apache.org/jira/browse/INFRA-18041
>             Project: Infrastructure
>          Issue Type: Bug
>          Components: JIRA
>            Reporter: Antoine Pitrou
>            Priority: Major
>
> In the Arrow JIRA, there are redundant link types to choose from when linking issues
together, such as:
> - "duplicates", "supercedes"
> - "is duplicated by", "is superceded by"
> - "dependency", "depends upon" (and perhaps "blocked", "is blocked by", "requires")
> - "dependent", "is depended upon by" (and perhaps "is required by")
> - "is contained by", "is part of" (and perhaps "is a child of", "parent feature")
> - "incorporates", "contains"
> It would be nice if those could be merged together. I would keep:
> - "supercedes"
> - "is superceded by"
> - "depends upon"
> - "is depended upon by"
> - "is part of"
> - "contains"
> cc [~wesmckinn] for opinions.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message