Permissions

Hello.

I’m trying to create a new ticket via email and keep getting this error. I
get the same message on both queues.

There has been an error:
There has been an error with your request:
You don’t have permission to create requests in this queue

Your message is reproduced below:

help

Of coarse the “Allow non-members to create requests” box is checked.

Suggestions/comments/sarcasm welcome.

Brad

I’m trying to create a new ticket via email and keep getting this error. I
get the same message on both queues.

There has been an error:
There has been an error with your request:
You don’t have permission to create requests in this queue

You can only create requests via a “correspond” queue. If this is an
action queue that is being mailed to, that might be the problem.

In /etc/aliases:

myqueue: “| /usr/local/rt/bin/rt-mailgate myqueue ”

must be “correspond” (not “action” or “comment”) for creation
to work, even if it’s turned on in the queue. At least this is how it
appears to me.

The ticket creation code is in
/usr/local/rt/lib/rt/ui/mail/manipulate.pm in the first subroutine in
this block:

elsif ($in_action eq ‘correspond’) {
if (!$serial_num) {

   # ....

I copied that code to the corresponding ‘elsif’ for “comment” queues
(removing the “no corresponding ticket” error code). I imagine the
same could be done for an action queue.

— Eric

Eric Goodman | “The opinions expressed by Eric do not
Workstation Support Group | represent the opinions of anyone who
UC Santa Cruz | matters.”
ericg@cats.ucsc.edu | — (modified from) “Cartoon Planet”

If your queue name has a space in it and you didn’t properly quote
the queue name in /etc/aliases, it will manifest like that.On Thu, May 11, 2000 at 04:32:51PM -0700, Eric Goodman wrote:

I’m trying to create a new ticket via email and keep getting this error. I
get the same message on both queues.

There has been an error:
There has been an error with your request:
You don’t have permission to create requests in this queue

You can only create requests via a “correspond” queue. If this is an
action queue that is being mailed to, that might be the problem.

In /etc/aliases:

myqueue: “| /usr/local/rt/bin/rt-mailgate myqueue ”

must be “correspond” (not “action” or “comment”) for creation
to work, even if it’s turned on in the queue. At least this is how it
appears to me.

The ticket creation code is in
/usr/local/rt/lib/rt/ui/mail/manipulate.pm in the first subroutine in
this block:

elsif ($in_action eq ‘correspond’) {
if (!$serial_num) {

   # ....

I copied that code to the corresponding ‘elsif’ for “comment” queues
(removing the “no corresponding ticket” error code). I imagine the
same could be done for an action queue.

— Eric


Eric Goodman | “The opinions expressed by Eric do not
Workstation Support Group | represent the opinions of anyone who
UC Santa Cruz | matters.”
ericg@cats.ucsc.edu | — (modified from) “Cartoon Planet”


rt-users mailing list
rt-users@lists.fsck.com
http://lists.fsck.com/mailman/listinfo/rt-users

jesse reed vincent – jrvincent@wesleyan.edu – jesse@fsck.com
pgp keyprint: 50 41 9C 03 D0 BC BC C8 2C B9 77 26 6F E1 EB 91
I have images of Marc in well worn combat fatigues, covered in mud,
sweat and blood, knife in one hand and PSION int he other, being
restrained by several other people, screaming “Let me at it!
Just let me at it!” Eichin standing calmly by with something
automated, milspec, and likely recoilless.
-xiphmont on opensource peer review

fixed.

did everyone know that UNIX is case sensitive?

ya…i know.From: rt-users-admin@lists.fsck.com
[mailto:rt-users-admin@lists.fsck.com]On Behalf Of Jesse
Sent: Thursday, May 11, 2000 4:51 PM
To: Eric Goodman
Cc: rt-users@fsck.com
Subject: Re: [rt-users] Permissions

If your queue name has a space in it and you didn’t properly quote
the queue name in /etc/aliases, it will manifest like that.

I’m trying to create a new ticket via email and keep getting this error.
I
get the same message on both queues.

There has been an error:
There has been an error with your request:
You don’t have permission to create requests in this queue

You can only create requests via a “correspond” queue. If this is an
action queue that is being mailed to, that might be the problem.

In /etc/aliases:

myqueue: “| /usr/local/rt/bin/rt-mailgate myqueue ”

must be “correspond” (not “action” or “comment”) for creation
to work, even if it’s turned on in the queue. At least this is how it
appears to me.

The ticket creation code is in
/usr/local/rt/lib/rt/ui/mail/manipulate.pm in the first subroutine in
this block:

elsif ($in_action eq ‘correspond’) {
if (!$serial_num) {

   # ....

I copied that code to the corresponding ‘elsif’ for “comment” queues
(removing the “no corresponding ticket” error code). I imagine the
same could be done for an action queue.

— Eric


Eric Goodman | “The opinions expressed by Eric do not
Workstation Support Group | represent the opinions of anyone who
UC Santa Cruz | matters.”
ericg@cats.ucsc.edu | — (modified from) “Cartoon Planet”


rt-users mailing list
rt-users@lists.fsck.com
http://lists.fsck.com/mailman/listinfo/rt-users

jesse reed vincent – jrvincent@wesleyan.edu – jesse@fsck.com
pgp keyprint: 50 41 9C 03 D0 BC BC C8 2C B9 77 26 6F E1 EB 91
I have images of Marc in well worn combat fatigues, covered in mud,
sweat and blood, knife in one hand and PSION int he other, being
restrained by several other people, screaming “Let me at it!
Just let me at it!” Eichin standing calmly by with something
automated, milspec, and likely recoilless.
-xiphmont on opensource peer review

rt-users mailing list
rt-users@lists.fsck.com
http://lists.fsck.com/mailman/listinfo/rt-users

fixed.

did everyone know that UNIX is case sensitive?

ya…i know.

Heh, I ran into that recently too.  The interesting thing is
that e-mail addresses /aren't/ case sensitive, so I assumed
anything else I put into the aliases file would act similarly.

J.D. Falk “Laughter is the sound
Product Manager that knowledge makes when it’s born.”
Mail Abuse Prevention System LLC – The Cluetrain Manifesto

Heh, I ran into that recently too. The interesting thing is
that e-mail addresses /aren’t/ case sensitive,

Emails can be case sensitive, though the very most mail servers threat
them case insensitive.

By a general rule, domains (everything at the left side of the @) if case
insensitive, though the servers might by theory do a difference (virtual
domains).

tobix@fsck.com

Alright - one last question for you guys to get me ‘off the ground,’ so to speak. I do appriciate the help and am sure your sick of me…

I successfully installed RT3 (easy as pie) on RedHat 7.3. I am using ‘sendmail’ and have created a symlink to the /etc/smrsh/ directory. Created the aliases, etc, etc. While I can create a ticket in rt and an outbound message is sent to the requestor, I cannot send requests in via E-Mail. I get an error back stating ['Subject: Ticket creation failed, Body: No permission to create tickets in the queue ‘General’.]

SO, I assume things are talking correctly a permission needs to be setup somewhere to allow ‘all mail’ sent to ‘rt@fusion…’ to process. How do I do this? I noted you need to make an adjustment to the ACL, however I cannot find this.

Regards,
Phillip

I think that somebody said here that to correct this you need to give the
unprivilidged group permission to create ticket.

If somebody is using EXCHANGE as the main mail repository I’ll be happy to
hear how you forward mail that comes to x@example.com mailto:x@example.com
to x@rt.example.com mailto:x@rt.example.com .

thanks!
/Shmulik.-----Original Message-----
From: Phillip Jackson [mailto:pjackson@arterystudio.com]
Sent: Mon, March 24, 2003 10:47 PM
To: rt-users@lists.fsck.com
Subject: [rt-users] Permissions

Alright - one last question for you guys to get me ‘off the ground,’ so to
speak. I do appriciate the help and am sure your sick of me…

I successfully installed RT3 (easy as pie) on RedHat 7.3. I am using
‘sendmail’ and have created a symlink to the /etc/smrsh/ directory. Created
the aliases, etc, etc. While I can create a ticket in rt and an outbound
message is sent to the requestor, I cannot send requests in via E-Mail. I
get an error back stating ['Subject: Ticket creation failed, Body: No
permission to create tickets in the queue ‘General’.]

SO, I assume things are talking correctly a permission needs to be setup
somewhere to allow ‘all mail’ sent to ‘rt@fusion…’ mailto:‘rt@fusion...’
to process. How do I do this? I noted you need to make an adjustment to
the ACL, however I cannot find this.

Regards,
Phillip

Lo all,

What permissions is needed on RT3 to allow a “take ticket” ?

I have a group specified on a queue, and I gave the group the following
permissions:
CreateTicket
OwnTicket
SeeQueue
ShowTicket

Then, I have assigned the “owner role” the following rights on the same
queue
CommentOnTicket
OwnTicket
ReplyToTicket
SeeQueue
ShowTicket
ShowTicketComments

Chris Knipe wrote:

Hence this email, what other permissions are required to allow a
authenticated user to take a ticket?

ModifyTicket ?
�|� Request Tracker... So much more than a help desk — Best Practical Solutions – Trouble Ticketing. Free.

ModifyTicket will allow the user to comment / reply to the ticket without
owning it (which is exactly what I don’t want).

Apparently a patch has been submitted to allow the functionality I require,
but it has not yet made it to the RT releases :((

me----- Original Message -----
From: “Phil Homewood” pdh@bestpractical.com
To: rt-users@lists.fsck.com
Sent: Monday, April 28, 2003 2:28 AM
Subject: Re: [rt-users] Permissions

Chris Knipe wrote:

Hence this email, what other permissions are required to allow a
authenticated user to take a ticket?

ModifyTicket ?

�|� Request Tracker... So much more than a help desk — Best Practical Solutions – Trouble Ticketing. Free.


rt-users mailing list
rt-users@lists.fsck.com
http://lists.fsck.com/mailman/listinfo/rt-users

Have you read the FAQ? The RT FAQ Manager lives at http://fsck.com/rtfm

ModifyTicket.On Fri, Apr 25, 2003 at 02:43:57PM +0200, Chris Knipe wrote:

Lo all,

What permissions is needed on RT3 to allow a “take ticket” ?

I have a group specified on a queue, and I gave the group the following
permissions:
CreateTicket
OwnTicket
SeeQueue
ShowTicket

Then, I have assigned the “owner role” the following rights on the same
queue
CommentOnTicket
OwnTicket
ReplyToTicket
SeeQueue
ShowTicket
ShowTicketComments

From what I can see, the setup works like I want to. When a user of the
first mentioned group logs in, the only thing he can do to a new ticket, is
to “take” it. Hence, the users in the group are required to own the ticket
before they can work on the ticket. However, when the user in the group
tries to take the ticket, RT responds with a permission denied error…
Hence this email, what other permissions are required to allow a
authenticated user to take a ticket?


me


rt-users mailing list
rt-users@lists.fsck.com
http://lists.fsck.com/mailman/listinfo/rt-users

Have you read the FAQ? The RT FAQ Manager lives at http://fsck.com/rtfm

Request Tracker... So much more than a help desk — Best Practical Solutions – Trouble Ticketing. Free.

How do you restrict a user from seeing a specific queue even exists? How do you restrict a privileged account from seeing anything other than the tickets they have requested?

Josh,

For Queues, don’t grant any permissions for Queues at the Global level.
Grant them for Roles or User-defined groups.

for restricting privileged users from seeing tickets they have NOT
requested, then grant “ShowTicket” to the Role of "Requestor, either for a
specific Queue or GLobally, if you want that kind of restriction applied
globally.

These answers are found in a couple RT books. Try to get them and read
them. Like reading an owners manual for a complicated piece of machinery.

Hope this helps.

KennOn Tue, Aug 28, 2012 at 10:00 AM, Josh Hopkins josh@prorivertech.comwrote:

How do you restrict a user from seeing a specific queue even exists? How
do you restrict a privileged account from seeing anything other than the
tickets they have requested?****