On 2/8/2006 Jesse answered a question thus:
Q: I’ve been starting to get to grips with the Approval functionality
(RT
3.4.2) and I’m wondering what determines who is allowed to approve
tickets
and who can see approvals on the Approvals screen.
A: Out of the box, that’s the owner. It should also be the adminccs, but
I don’t think that’s there yet.
I would like to be able to have approvals visible to all members of a
group, and approvable by any one of them. Has this been added? If not,
do we have an ETA? Is there another mechanism I could use to make this
function happen?
On 2/8/2006 Jesse answered a question thus:
Q: I’ve been starting to get to grips with the Approval functionality
(RT
3.4.2) and I’m wondering what determines who is allowed to approve
tickets
and who can see approvals on the Approvals screen.
A: Out of the box, that’s the owner. It should also be the adminccs, but
I don’t think that’s there yet.
I would like to be able to have approvals visible to all members of a
group, and approvable by any one of them. Has this been added? If not,
do we have an ETA? Is there another mechanism I could use to make this
function happen?
There is an example in the wiki covering exactly this behaviour:
http://wiki.bestpractical.com/view/ApprovalCreation
→ Group Approvals
Emmanuel Lacour ------------------------------------ Easter-eggs
44-46 rue de l’Ouest - 75014 Paris - France - M�tro Gait�
Phone: +33 (0) 1 43 35 00 37 - Fax: +33 (0) 1 41 35 00 76
mailto:elacour@easter-eggs.com - http://www.easter-eggs.com
Emmanuel,
Have you looked at the QA WorkFlow design document I sent to the RT
Docs subversion archive? It has an Approvals portion in it. It is
designed around a front-end queue that acts as a collection of requests
waiting for approval. The normal RT privileges can be applied (like
creating a group and granting privileges for the members to
see/approve/move ticket to support queue) as well as any specific
notifications to let requestors know that their request is 1)being
looked at, 2)approved, 3)rejected (with comments), etc. Of course, it
requires an AdminCc to oversee it, but the basic design is there AND the
ticket numbers tay the same (great for auditability).
Kenn
LBNLOn 1/30/2008 1:20 AM, Emmanuel Lacour wrote:
On Tue, Jan 29, 2008 at 02:55:35PM -0800, Roger Mastrude wrote:
On 2/8/2006 Jesse answered a question thus:
Q: I’ve been starting to get to grips with the Approval functionality
(RT
3.4.2) and I’m wondering what determines who is allowed to approve
tickets
and who can see approvals on the Approvals screen.
A: Out of the box, that’s the owner. It should also be the adminccs, but
I don’t think that’s there yet.
I would like to be able to have approvals visible to all members of a
group, and approvable by any one of them. Has this been added? If not,
do we have an ETA? Is there another mechanism I could use to make this
function happen?
There is an example in the wiki covering exactly this behaviour:
ApprovalCreation - Request Tracker Wiki
→ Group Approvals
Emmanuel,
Have you looked at the QA WorkFlow design document I sent to the RT
Docs subversion archive? It has an Approvals portion in it. It is
designed around a front-end queue that acts as a collection of requests
waiting for approval. The normal RT privileges can be applied (like
creating a group and granting privileges for the members to
see/approve/move ticket to support queue) as well as any specific
notifications to let requestors know that their request is 1)being
looked at, 2)approved, 3)rejected (with comments), etc. Of course, it
requires an AdminCc to oversee it, but the basic design is there AND the
ticket numbers tay the same (great for auditability).
Pretty interesting, I will look at your doc 
Emmanuel Lacour ------------------------------------ Easter-eggs
44-46 rue de l’Ouest - 75014 Paris - France - M�tro Gait�
Phone: +33 (0) 1 43 35 00 37 - Fax: +33 (0) 1 41 35 00 76
mailto:elacour@easter-eggs.com - http://www.easter-eggs.com