Hi James, >> Hmm. Didn't even know this issue comes from TCM. Anyway. >> > It does.
Perhaps a policy to add some "TCM:" in front of the summary of such issues might be worth considering. While this doesn't *automatically* mean the issue does get more attention, it could make a developer spend a few minutes to see if there's a quick fix. At least those developers who care to not waste QA resources :) > There is a test to look at the alignment functionality in a table. > I don't know why this is implemented here and not in a report. In my mind, it > does not make much sense to align a field in a table in a certain fashion, but > in a report it very much does. I suppose this is a relict from this dialog being re-used - it was created for other purposes (use in Writer/Calc), and re-used for the tables. >> As much as I understand that it's frustrating to report/QA bugs which >> don't get attention for years, that's, as said in another thread here, a >> matter of resources and priorities. >> > I am well aware of this limitation. I was questioning if it even was worth > looking into as I don't think this feature is even used much in the real > world. Not sure. I myself like to display table content centered. If we had quick and easy reporting, I probably need this for tables, but alas ... >> And, in the hope this doesn't sound too harsh: I would not be willing to >> spend any (non-negligible) amount of time into an issue just to satisfy >> TCM (or any other QA process, for that matter). That is, if the bug does >> have a very limited impact only *in real life* (as indicated by the >> priority), then I'd consider it a waste of precious resources to fix it >> before the more important issues. > > You will not get an argument out of me on this. Hmm. Not sure whether this means you were offended by what I said ... > TCM needs more than just a small space for an issue as you have to go look > up the issue to see if it affects the platform you are testing on and if > it has been fixed or not. This would help greatly in the TCM QA effort. > Maybe another issue to file? I don't have an opinion here, as I don't know TCM myself (and all our QA folks which could explain it to me is not in the office, yet :). I'd simply imagine something like a tag "don't test this item, it's broken, which is issue #i12345#", so you guys can ignore it. Not sure if that's feasible. Ciao Frank -- - Frank Schönheit, Software Engineer [EMAIL PROTECTED] - - Sun Microsystems http://www.sun.com/staroffice - - OpenOffice.org Base http://dba.openoffice.org - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
