[prev in list] [next in list] [prev in thread] [next in thread]
List: rt-devel
Subject: [Rt-devel] re-assigning tickets
From: "Olly Stephens" <Olly.Stephens () arm ! com>
Date: 2008-12-17 9:13:02
Message-ID: DD2D1CDF962D7346A5B0E5EE9CA361270FF1C38A () ZIPPY ! Emea ! Arm ! com
[Download RAW message or body]
--===============0274521704==
Content-Class: urn:content-classes:message
Content-Type: multipart/alternative;
boundary="----_=_NextPart_001_01C96027.CDC3ABCA"
This is a multi-part message in MIME format.
Hi,
Just ran into the problem that nobody (not even superuser) can reassign
a request in a single shot. They have to steal then reassign.
I noticed a workaround for superusers on the wiki
(http://wiki.bestpractical.com/view/AllowSuperUserToReassignTickets) but
has anyone considered adding a 'ReassignTicket' right to allow this
check to be overridden, thereby solving it in a more sane way? Or is
there some workflow problem I'm not thinking about when I suggest this.
The real scenario behind this is dealing efficiently with staff
absences; ideally we'd like to be able to say that user X has complete
rights over tickets owned by user Y, but that's a more complicated thing
to code up - adding a simple ACL so that user X doesn't have to steal
the ticket from Y first in order to assign it to Z should be trivial in
comparison.
If I made the change, is it likely that it'd be incorporated into the
core?
Thanks in advance,
Olly
--
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and \
may also be privileged. If you are not the intended recipient, please notify the \
sender immediately and do not disclose the contents to any other person, use it for \
any purpose, or store or copy the information in any medium. Thank you.
[Attachment #3 (text/html)]
<html xmlns:v="urn:schemas-microsoft-com:vml" \
xmlns:o="urn:schemas-microsoft-com:office:office" \
xmlns:w="urn:schemas-microsoft-com:office:word" \
xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" \
xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;}
@page Section1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.Section1
{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=EN-GB link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal>Hi,<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>Just ran into the problem that nobody (not even superuser)
can reassign a request in a single shot. They have to steal then
reassign.<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>I noticed a workaround for superusers on the wiki (<a
href="http://wiki.bestpractical.com/view/AllowSuperUserToReassignTickets">http://wiki.bestpractical.com/view/AllowSuperUserToReassignTickets</a>)
but has anyone considered adding a ‘ReassignTicket’ right to allow
this check to be overridden, thereby solving it in a more sane way? Or is
there some workflow problem I’m not thinking about when I suggest \
this.<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>The real scenario behind this is dealing efficiently with
staff absences; ideally we’d like to be able to say that user X has
complete rights over tickets owned by user Y, but that’s a more
complicated thing to code up – adding a simple ACL so that user X doesn’t
have to steal the ticket from Y first in order to assign it to Z should be
trivial in comparison.<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>If I made the change, is it likely that it’d be
incorporated into the core?<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>Thanks in advance,<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>Olly<o:p></o:p></p>
</div>
</body>
<!--[object_id=#arm.com#]--><P align=left><FONT face=Arial size=1>-- </FONT></P>
<P align=left><FONT face=Arial size=1>IMPORTANT NOTICE: The contents of this email \
and any attachments are confidential and may also be privileged. If you are not the \
intended recipient, please notify the sender immediately and do not disclose the \
contents to any other person, use it for any purpose, or store or copy the \
information in any medium. Thank you.</FONT></P></html>
_______________________________________________
List info: http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-devel
--===============0274521704==--
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic