513 - Allow non-authors to verify fixed tickets

What is the enhancement in mind? How should it look and feel?

Since QA people are hard to come by and I like to abuse the community at large for testing purposes, it seems like it'd be a good idea to let normal users to mark fixed tickets as verified.

This could theoretically be an option that authors can set on their projects.

User When Change
Torhal Jul 24, 2013 at 22:03 UTC Changed status from New to Declined
Torhal Jun 03, 2011 at 16:56 UTC Changed assigned to from None to prencher
Ackis Feb 01, 2011 at 18:01 UTC Changed assigned to from ckknight to None
Ackis Mar 27, 2009 at 19:47 UTC Changed component from None to Component #15
Ackis Jan 19, 2009 at 18:19 UTC Changed assigned to from None to ckknight
ckknight Aug 11, 2008 at 19:15 UTC Create

You must login to post a comment. Don't have an account? Register to get one!

  • Avatar of x87bliss x87bliss Mar 19, 2010 at 20:21 UTC - 0 likes

    What about setting up a "poll" kind of system. People could vote the fix as either verified or not. If after a certain period of time the author does not manually update the ticket, it'll be marked as verified or not by the popular vote.

    It should be restricted that each unique username gets one vote; however, they should be allowed to change or withdraw their vote if necessary (as long as the do so during the voting window).

  • Avatar of Zasurus Zasurus Sep 26, 2009 at 10:22 UTC - 0 likes

    This could also be time specific. So for example if the original poster hadn't replied in a week then two or three other posters could mark it as fixed. :-)

  • Avatar of seppyk seppyk Jan 16, 2009 at 17:11 UTC - 0 likes

    If this is implemented, I would like a configuration option relating to this to provide a bit more control.

    I am supportive of non-project members taking a more active role in project management, but for certain defects or projects, I would only want to allow non-project members to verify defects/enhancements for tickets they were the original submitter.

    If desired, this would provide more control and not allow random non-project members to go in verifying any random defect.

  • Avatar of Zyuu Zyuu Aug 11, 2008 at 20:32 UTC - 0 likes


  • Avatar of Arrowmaster Arrowmaster Aug 11, 2008 at 19:20 UTC - 0 likes

    Ckknight just wants to abuse me more to fix his stuff for him =(

    Oh wait I can already do this....


  • Avatar of Ackis Ackis Aug 11, 2008 at 19:18 UTC - 0 likes

    A check and balance situation would be nice... for example we have an approved list of QA they can verify solo, however a threshold for random verifications would be nice. Joe user and bob user would both have to verify before it gets set to "verified". For the threshold a custom value for each project would also help (ie: if I want 5 people to verify, I can set it to 5).




Last updated
Jul 24, 2013
Aug 11, 2008
Declined - We decided not to take action on this ticket.
Enhancement - A change which is intended to better the project in some way
Medium - Normal priority.

Reported by

Possible assignees