Hash: SHA1

On Friday January 16, 2009, Andy Kurth wrote:
> We need to decide how the "Fix Version" property is handled when resolving
> an issue.  A description of this property at:
> http://www.atlassian.com/software/jira/docs/v3.11/projects.html#versions
> Fix Version(s) - this is the version(s) in which the issue was (or will be)
> fixed. For instance, the bug affecting versions 1.1 and 1.2 might be fixed
> in version 2.0. Note that issues which do not have a Fix Version are
> classified as 'Unscheduled', as shown in the screenshot above.
> I'm thinking this property would always be set to the next unreleased
> version but I'm confused because the property can be multivalued.  What
> does everyone think of leaving this set to "Unknown" when a developer
> resolves an issue.  When the issue is tested before a version is released,
> the tester can set the "Fix Version".
> -Andy

I'm thinking the reason the property can be multivalued is to allow for fixes 
when multiple major versions are being maintained.  For example, say programX 
maintains both 1.x and 2.x series releases.  Let's say they're most recent 
releases are 1.5 and 2.1.  They may have a bug that comes up that affects 
both 1.5 and 2.1.  So, the Affects Versions property would be set to both 1.5 
and 2.1.  Then, if it's a critical issue, they may release 1.5.1 and 2.1.1 
that both contain the fix, requiring that the Fix Versions property be set to 
both 1.5.1 and 2.1.1.

Since we're not maintaining more than one series of release, I'd say we just 
go ahead and set it to the next unreleased version when the issue is 

That's my $0.02


- -- 
- -------------------------------
Josh Thompson
Systems Programmer
Virtual Computing Lab (VCL)
North Carolina State University


my GPG/PGP key can be found at pgp.mit.edu
Version: GnuPG v1.4.6 (GNU/Linux)


Reply via email to