I think it is important that as much as possible issues be properly
flagged as affects-version including all of the versions they affect,
not just the lowest version in which the issue obtains and implicitly
later versions since it hasn't been marked resolved. Having
affects-version flags reflecting reality makes it feasible to query Jira
for the report of known issues affecting a particular version.
If an issue is only flagged as affecting 2.5.0 and not resolved, it will
not appear on a query for issues known to affect 2.5.3.
Including a query for unresolved 2.5.0 issues in your reporting on
issues affecting 2.5.3 doesn't hit the mark because the issue may have
been resolved for 2.5.4, or for 2.6, but not for 2.5.3, and so this will
under-report defects affecting 2.5.3.
I don't think we can get around the affects-version flag needing to be
correct to get the reporting that's useful to have. So I think the
problem is an organizational one of what workflow will result in the
flag being kept up to date. And how do we resolve the many easy defects
so that we're not spending time on administrivia when we could just as
easily fix the issue already and be done with it.
Jason Shao wrote:
On Jul 11, 2007, at 12:21 PM, Jennifer Bourey wrote:
Just out of curiosity, how are these affects-version attributes
maintained? Are we expected to go through open JIRA tickets every
time a JIRA release is added? I believe this ticket was created
before RC2 was released.
Not entirely well defined. Maybe a good chance to clarify.
I would propose:
In general - the first known version affected by/exhibiting a
particular issue.
Unless - the issue gets patched/fixed in multiple branches in which
case it seems appropriate to also include lower point releases of a
higher branch than the lowest one patched:
e.g. if it's patched in 2.5.4 & 2.6.1 it seems worthwhile to list
affects 2.5.0 & 2.6.0
Jason
--
You are currently subscribed to [email protected] as: [EMAIL
PROTECTED]
To unsubscribe, change settings or access archives, see
http://www.ja-sig.org/wiki/display/JSG/uportal-dev
