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 |
|---|---|---|
| Ackis | Fri, 27 Mar 2009 19:47:26 | Changed component from None to Ticket System |
| Ackis | Mon, 19 Jan 2009 18:19:43 | Changed assigned to from None to ckknight |
| ckknight | Mon, 11 Aug 2008 19:15:43 | Create |
- 5 comments
- 5 comments
Facts
- Last updated on
- 12 Oct 2009
- Reported on
- 11 Aug 2008
- Status
- New - Issue has not had initial review yet.
- Type
- Enhancement - A change which is intended to better the project in some way
- Priority
- Medium - Normal priority.
- Component
- Ticket System
- #5
Zasurus Sat, 26 Sep 2009 10:22:21This 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. :-)
- #4
seppyk Fri, 16 Jan 2009 17:11:48If 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.
- #3
Zyuu Mon, 11 Aug 2008 20:32:40Hi.
- #2
Arrowmaster Mon, 11 Aug 2008 19:20:02Ckknight just wants to abuse me more to fix his stuff for him =(
Oh wait I can already do this....
MORE PEOPLE MUST JOIN ME IN THE SUFFERING!
- #1
Ackis Mon, 11 Aug 2008 19:18:56A 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).