Please simplify issue tracker
Posted: Thu Jun 05, 2008 3:16 pm
Hi,
I've been trying to switch to OOO for several years now and sympathize strongly with the application-suite. Since I'm mainly on Mac, and with 3.0 we'll get a native version I'm in good hopes for the future that I can switch fully towards the end of the year. I would like to contribute to QA by issuing bug reports, but I find it terribly difficult to do so.
I have a proposal to make.
Please allow a registered user to create a profile with the current ooo version he/she is using - and allow to enter issue-tracking land based on that profile. So if I browse issues or submit issues I am automatically only confronted with issues relevant to my workspace/ooo-version.
The query form of the issue tracker is incredibly complicated and I have no idea what 90% of the abbreviations in the various lists mean. I use OOO 3.0 beta on the Mac and I want a simple way to prevent, that if I query issues for "crash on closing application" a am not confronted with existing issues for OOO 1.1 RC1.
If - as the recent innovations in the OOO-site indicate - OOO-managers feel there is not enough QA-feedback from users, I think this would be a highly useful enhancement.
Best
panca
I've been trying to switch to OOO for several years now and sympathize strongly with the application-suite. Since I'm mainly on Mac, and with 3.0 we'll get a native version I'm in good hopes for the future that I can switch fully towards the end of the year. I would like to contribute to QA by issuing bug reports, but I find it terribly difficult to do so.
I have a proposal to make.
Please allow a registered user to create a profile with the current ooo version he/she is using - and allow to enter issue-tracking land based on that profile. So if I browse issues or submit issues I am automatically only confronted with issues relevant to my workspace/ooo-version.
The query form of the issue tracker is incredibly complicated and I have no idea what 90% of the abbreviations in the various lists mean. I use OOO 3.0 beta on the Mac and I want a simple way to prevent, that if I query issues for "crash on closing application" a am not confronted with existing issues for OOO 1.1 RC1.
If - as the recent innovations in the OOO-site indicate - OOO-managers feel there is not enough QA-feedback from users, I think this would be a highly useful enhancement.
Best
panca