On Jul 11, 2007, at 1:03 PM, Andrew Petro wrote: > 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.
Generating and maintaining that metadata is likely to be expensive. I wonder if search based criteria like "open issues with affects <= current.version" is a more sustainable model in the long run. It's also consistent with the way we use resolved -- we use them to timebox periods we know an issue is open, etc. Jason -- Jason Shao Application Developer Rutgers University, Office of Instructional & Research Technology v. 732-445-8726 | f. 732-445-5539 | [EMAIL PROTECTED] | http:// jay.shao.org -- 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
