www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matt Foley (JIRA)" <j...@apache.org>
Subject [jira] [Created] (INFRA-3937) Request for Hadoop Jiras: add custom field "Target Version/s" [field type Version Picker]
Date Mon, 19 Sep 2011 21:01:10 GMT
Request for Hadoop Jiras: add custom field "Target Version/s" [field type Version Picker]
-----------------------------------------------------------------------------------------

                 Key: INFRA-3937
                 URL: https://issues.apache.org/jira/browse/INFRA-3937
             Project: Infrastructure
          Issue Type: Improvement
      Security Level: public (Regular issues)
          Components: JIRA
            Reporter: Matt Foley


The Hadoop community actively maintains sustaining releases from non-trunk branches.  As a
result, critical bug fixes may be targeted for, and fixed in, multiple releases in different
code lines.  In Jira, the fact that 'fixVersion' is a Multi-Select type field partially accommodates
this need.  However, we also need a 'targetVersion' field.  Here's why:

When making a release, one wants to query all Jiras marked fixed in this release.
Also, one wants to be able to query all open issues targeted for this release, but not yet
fixed.
Neither of these queries can be made reliably if a bug fix is targeted for two or more versions,
and fixed in some but not all.

Why current usage is deficient:  Currently the Fix Versions is being overloaded.  It is used
to mean "should be fixed in" (target versions) while the bug is open, and "is fixed in" (fix
versions) after the bug is resolved.  That's fine if there's only one code branch in use.
 But if a fix is targeted for two branches A and B, and it's actually committed to A but not
yet to B, there's no way to query the state of the fix.  The bug appears open for both (or
sometimes it's incorrectly closed for both!).  You have to manually visit the individual bug
report and review the SubversionCommits.  This might be automatable, but it sure isn't easily
expressed.

If we add a Target Versions field, then intent and completion can be separately marked (in
the Target Versions and Fix Versions, respectively), and simple queries can clearly differentiate
the cases. 

This request applies to Jira products HADOOP, HDFS, and MAPREDUCE.
TargetVersion should be the same field type as FixVersion, apparently Version Picker or Multi-Select.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message