https://issues.apache.org/ooo/show_bug.cgi?id=123063
Oliver-Rainer Wittmann <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #6 from Oliver-Rainer Wittmann <[email protected]> --- I somehow agree with Rainer. My scenario which would benefit from the existence of a value like 'pre 3.4.0' for field Version: In the last days I reviewed certain defects reported on version 4.0.0 - value of field Version = 4.0.0. My investigation reveals for some of them already occur in AOO 3.4.0, but not in OOo 3.3.0. Thus, I changed value of field Version to 3.4.0 while setting Latest Confirmation on to 4.0.0. Some are reproducible in OOo 3.3.0 as well. Here, I also changed the value of field Version to 3.4.0 loosing the possibility to distinguish between these issues. My opinion of field Target Milestone: This field should only be set, when it is 100% clear that the issue is solved in a certain version - as it is more or less documented. To request a solution for a certain version we are using our flags. Thus, may be it makes sense to restrict the access to this field to the corresponding group. And yes - as Rainer said - having values for former releases would enable us to document that a submitted issue from a user using a former version has been fixed in an already available release. This is not really critical, but would have a documentary purpose. I am not sure, if we would need values for former released versions for field Latest Confirmation on, when we would have values for former released versions for field Target Milestone. For solved issues we have Latest Confirmation on == Target Milestone - 1 -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug. You are watching all bug changes.
