Hi all,
well the subject could also read "please set correct keywords when
working on issues".
Wihtin the last days I started do do my daily qa-job and was going to
confirm some issues.
So .. what I do is to look for unconfirmed defects without keyword "oooqa".
Great! I found 14 P2 issues .. so there is really something important to
me to do.
So .. let's have a look:
1st issue ... *wow* what a heck of discussion .. there are already
developers talking to the user (so .. nothing to do for me)
2nd issue .. same again (ok this time a discussion by qa members)
3rd issue ... guess what .. comments from qa / developer .. they even
seem to have an idea for the root cause
4th .. comments
5th .. reassigened to requirements, but still a defect?
6th .. comments ...
(btw. I'm getting a little tired checking all thoses comments)
7th .. oh great really something to get into and help
8th .. comments
.. and so on. I gave up, as I wondered if I should waste more time
reading a lot of comments.
So *please* all .. set the oooqa keyword, if you are already
investigating an issue. This will help others to save time and take care
about those poor little issues nobody cares for yet.
André
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
