By Leeteq on
Posting it here for some feedback before deciding to file a feature request.
Wouldnt it be practical if it was possible for users with a specific role to tick off a "verified as bug" mark on issues filed as "bug report"? That coudl then be shown in a separate column in the issue tracker queue page, not having to open every one and read to find out which are indeed bugs.
This can be useful in many respects. Would enable many people to save time and unnecessary page loads when checking for bugs and not "anything reported as a bug".
It could also have its own RSS feed, one general, one per project.
Comments
Could be done with dedicated status entry too, perhaps
It is possible to achieve sucn an effect by adding a dedicated status entry for this, I guess. However, that has its own undesired consequences. I havent thought through all possibilities or implications. Open for discussion :-)
.
--
( Evaluating the long-term route for Drupal 7.x via BackdropCMS at https://www.CMX.zone )
Best practice
If someone mis-files an issues as a bug, someone has to review it. If it isn't a bug, the reviewer should simply change the issue status. I do this all the time, typically turning bug reports into 'feature requests.'
That said, a "bug verified" status might have some merit for core reviewers if people were willing to use the new status flag.
--
http://ken.blufftontoday.com/
http://new.savannahnow.com/user/2
Search first, ask good questions later.
My point is to distinguish between acknowledged and "potential"
Well, this is not a suggestion to try to avoid mis-filing issues. That is a different issue, and one that is probably only solved by adjusting it as it works now. Don't see any problems with that.
The reason for this suggestion is to help us save time and spot and follow-up easier, AND to raise everyone's awareness on what is actually acknowledged as a bug (and hence can be expected to be fixed - or postponed - which in itself is a useful combination that suggest a separate checkmark and not a new status for this).
There is an ocean of examples here on discussions going on about issues where it is clear only after or well into reading the discussion that this can be viewed as a bug IF we agree that it should be required from the current functionality, or as a feature request if we conclude that the current version was not (yet) designed to "do this" or "work like that". Other variations exist as well. I think most of us are experiencing some of them regularly.
There is still only 24 hours in a day, and we are probably all somewhat involved in fighting harder and harder to make the most of it. I am certain that as a whole, loads of people here is spending a significant amount of time just reading through to see if something is relevant or "ready yet", and that takes away time we could spend actually communicating, collaborating and contributing more. I am sure Drupal.org would benefit from enabling their users to be efficient wherever possible.
This could even help reduce some strain on the server (page loads) too. But mostly I think it would be very practical to be able to follow those that are verified closer and easier than what is the situation now.
A dedicated check mark (with a column in the main view) would be best, keeping the status entries as they are, without the need to change or update anything other than start checking that tickmark as we move along. That should not be available to update for "anyone", though. Possibly only for the module maintainers etc.
.
--
( Evaluating the long-term route for Drupal 7.x via BackdropCMS at https://www.CMX.zone )