Apache OpenOffice (AOO) Bugzilla – Issue 3354
We need a resolution state for incomplete bug reports
Last modified: 2021-05-27 19:28:19 UTC
Hi, in the moment there's no real state to flag a bug with a lack of information. You can set them to 'invalid' or 'worksforme' but in most cases this doesn't match the intended goal. A new flag called i.e. 'incomplete' would give an better overview on open tasks and unexperienced bug reporters would better understand what you want from them. Thanks, Peter QA - StarOffice
Try using "Invalid" and explain the difficulty. louis
Hi Louis, invalid and incomplete describe different states. Invalid means that the issue isn't an issue at all. Incomplete should indicate that there is (or could be) an issue but the submitter hasn't given all the information he should. For this case invalid is to harsh. This may cause some people loose interest in reporting bugs. Best regards, Peter BTW: Sorry for the late answer but I didn't find any email in my intray. Could it be that automaticly generation is broke.
PING ;-)
mozilla.org uses qawanted keywords for this purpose. needhelp is already adopted from mozilla.org. qawanted should work as well and make transitioning of mozilla.org developers to this BugZilla variant easier.
Not sure if a keyword is the better solution - it can be overlooked more easily. I definately agree with Peter that there is a problem - currently, we can only use workarounds (ask in the bug, wait, and then close the bug if there is no response). This is pretty unsatisfying. We need a method to clearly indicate "We're willing to deal with this bug, but are missing information to reproduce it". Louis, is there any chance that the Scarab will feature this?
What about leaving the issue assigned to the user who needs to respond? It'll be clear to all involved that the issue is pending comment and the user will also get email reminders. I agree w/ Louis's recommendation also, closing an issue as invalid and asking for more information is a better way to go. Sounds like a process review may help more than adding a new feature.
@Kenneth: Hi, of course your suggestion is state of the art for correct workflow in QA. Normally a task should be with the person who's to take action. Unfortunately not everybody played the correct moves at the right time. We moved away from this practice not too long ago because we had a enormous stack of 'forgotten' issues asigned to people all over the world. @Michael: I'm now assigning it to you because you're the one in charge to speak for the QA project. Best regards, Peter
I don't see the need of an incomplete state: * if an issue is initially inclomplete, reassign to committer and ask for full information. * if additional information is needed during lifetime of an issue, just file a new issue and make it dependent to the current one. so you have the complete overview. so please explain me, why we need an additional state ?!
Martin et al, I want to have _less_ issues in the system, not _more_ than we already have. Your suggestion: "if an issue is initially inclomplete, reassign to committer and ask for full information". No, please never. Those are the bugs, that will get lost in the system forever. I want the competent people to be owners of the bugs. If something is missing, write a comment, but stay the owner. The submitter gets an email notification. If you don't get an answer withing lets say two weeks, close the issue, kindly offering the possibility to re-open. I agree that a status "incomplete" would be great, because then people could jump on those, but honestly: who will ever do that? I would still say that this issue should be handled as an RFE for Scarab.
Would be great if we could handle the new status "incomplete" as a valid RFE for the successor of IssueZilla.
Update: In Project Tracker (IssueZilla's successor), Domain Administrators and Project Owners will be able to define these values themselves. Action plan: Reassigning to pj for review. This is an issue for discussion with openoffice administrators, perhaps Stefan. Thanks, Kristen
@Stefan: I agree with Kristen. You're opinion would be quite useful. Please consider also that the indroduction of this flag would also ease alignment of workflow for StarOffice internal and external bugtracking. Best regards, Peter @All: Reasigning it to default owner. Everybody should feel free to add hers/his two cents.
- MS agreed that this state would make sense - collab.net said it IZ' successor, it will be possible for Domain Administrators to define such values => IMO, the next person to take action is Stefan, once the new system is in place. Leaving this issue with issues@www doesn't make sense now, IMO ....
I also agree, that the ability to introduce a new states is a great improvement. Reassigning to support for resolving as resolved/later and status whiteboard update. Thanks, Stefan
Closing this as resolved later and updated the whiteboard.
Setting the milestone as 'CEE Consid-future'. Regards, Karishma Support Operations
Reopening to update the status. -Jeeva CollabNet Support
Marking this as Resolved/Fixed per CollabNet's policy as the feature is available in Project Tracker, the successor of Issue Tracker. -Jeeva CollabNet Support