Re: [rt-users] Owner not showing in search results?

Never mind the SQL logging question, I got it. Something really weird: in the ticket insertion, I see no owner value at all. Here it is: INSERT INTO Tickets (Resolved, Priority, Starts, Creator, InitialPriority, SLA, Created, LastUpdatedBy, Type, Queue, LastUpdated, Started, Due, Subject,

[rt-users] Manage Group Memberships via REST API

Hello, At the moment I don't see a way to do this, but I just wanted to make sure I wasn't missing anything. When we terminate employees that had access to RT, we put them into a group called Terminated Employees. Being a member of this group will re-assign any tickets they owned, on reply,

Re: [rt-users] no alert for invalid mail addresses

Petr Hanousek writes: >Hi geeks, >sometimes someone here mistypes the mail address of Requestor or CC. The >typos in addresses are various, my question is about the really obvious >ones. Like if you put to CC an address "a@b". Is there any mechanism in >RT to detect such mistakes and say something

Re: [rt-users] Owner not showing in search results?

On Mon, Nov 28, 2016 at 11:41 AM, Kenneth Marshall wrote: > On Mon, Nov 28, 2016 at 11:32:36AM -0500, Alex Hall wrote: > > Thanks, I didn't know that would happen. I did that to suppress the > email notification; we want users notified if their tickets change owners, > but only if

Re: [rt-users] __active__ including stalled tickets?

On 05/01/17 11:12 AM, Matt Zagrabelny wrote: ...and I see that Shawn has answered, too. Here is what I had to say: "stalled" is an active status. I know the word feels "inactive", but according to the default lifecycle, it is active.

Re: [rt-users] How unprivileged users could see all tickets in their queue?

Hi, In your example you said : "I've got 2 unprivileged users with a single queue, each being the owner of multiple tickets in that queue." But in my case, the users is a customer, and they never owner of the tickets. So, the users see only the tickets they are requestor. I would like to

Re: [rt-users] __active__ including stalled tickets?

Okay, I can see that. I was thinking of active/inactive as now, as in a stalled ticket is inactive until someone un-stalls it. But from RT's perspective, it does make sense that a ticket not deleted or resolved is still, in some way, active. I'll have to adjust my crontool script too, or people

Re: [rt-users] __active__ including stalled tickets?

...and I see that Shawn has answered, too. Here is what I had to say: "stalled" is an active status. I know the word feels "inactive", but according to the default lifecycle, it is active. https://github.com/bestpractical/rt/blob/stable/etc/RT_Config.pm.in#L3034 On Thu, Jan 5, 2017 at 10:07 AM,

Re: [rt-users] __active__ including stalled tickets?

> On Jan 5, 2017, at 10:56, Alex Hall wrote: > > Hey all, Hi Alex, > I just did a search: > Priority > 9 and Status = '__active__' > Five of the resulting tickets are stalled, but I thought __active__ ignored > stalled tickets. Any idea why they're appearing? Did I miss a

Re: [rt-users] __active__ including stalled tickets?

On Thu, Jan 5, 2017 at 11:01 AM, Matt Zagrabelny wrote: > __Active__ is case sensitive, I believe. > I should have said that I tried capital and lowercase A in my searches, along with making the word all caps. I keep getting the same result. > -m > > On Thu, Jan 5, 2017 at

Re: [rt-users] no alert for invalid mail addresses

On Thu, Jan 5, 2017 at 9:59 AM, Petr Hanousek wrote: > Thank you Matt, this will also help. BTW, for the curiosity, the "Merge > with an alternate user" option behaves the same way like > http://search.cpan.org/~bps/RT-Extension-MergeUsers/lib/RT/Extension/MergeUsers.pm > or

Re: [rt-users] __active__ including stalled tickets?

__Active__ is case sensitive, I believe. -m On Thu, Jan 5, 2017 at 9:56 AM, Alex Hall wrote: > Hey all, > I just did a search: > Priority > 9 and Status = '__active__' > Five of the resulting tickets are stalled, but I thought __active__ ignored > stalled tickets. Any idea

Re: [rt-users] no alert for invalid mail addresses

Thank you Matt, this will also help. BTW, for the curiosity, the "Merge with an alternate user" option behaves the same way like http://search.cpan.org/~bps/RT-Extension-MergeUsers/lib/RT/Extension/MergeUsers.pm or does it have some extra functionality? But my main focus with this question was

[rt-users] __active__ including stalled tickets?

Hey all, I just did a search: Priority > 9 and Status = '__active__' Five of the resulting tickets are stalled, but I thought __active__ ignored stalled tickets. Any idea why they're appearing? Did I miss a setting or something, or is this intended behavior? Thanks. -- Alex Hall Automatic

Re: [rt-users] no alert for invalid mail addresses

Hi Petr, We have this problem a lot. BP wrote us this module to help manage autocreated users that don't belong in the database: https://github.com/bestpractical/rt-extension-manageautocreatedusers -m On Thu, Jan 5, 2017 at 3:53 AM, Petr Hanousek wrote: > Hi geeks, >

Re: [rt-users] How unprivileged users could see all tickets in their queue?

Hi, No need to add the custom role to the tickets, just to the queue. Best Regards Martin On 2017-01-05 14:26, Felix Defrance wrote: Le 05/01/2017 à 12:22, Alex Hall a écrit : Martin's suggestion makes sense, but I thought Felix was trying to restrict user search, not ticket search? That

Re: [rt-users] How unprivileged users could see all tickets in their queue?

Ah, got it. If you want to restrict users from seeing the user search option, and from searching tickets, it seems like both Martin's and my emails will do it. The only potential problem I see with mine is that one could still type in a username, though queue/group restrictions should still stop

Re: [rt-users] How unprivileged users could see all tickets in their queue?

Le 05/01/2017 à 12:22, Alex Hall a écrit : > Martin's suggestion makes sense, but I thought Felix was trying to restrict > user search, not ticket search? That is, he doesn't want users to be able to > search (and thus view the names of) all users? It's quite early here, so my > brain may

Re: [rt-users] How unprivileged users could see all tickets in their queue?

Martin's suggestion makes sense, but I thought Felix was trying to restrict user search, not ticket search? That is, he doesn't want users to be able to search (and thus view the names of) all users? It's quite early here, so my brain may still be muttled and I could be wrong. Sent from my

Re: [rt-users] How unprivileged users could see all tickets in their queue?

Hi Félix, I've just tried to configure this on a RT 4.4.1 install using a custom role and it seems to work fine. Here is the process I carried out. I've got 2 unprivileged users with a single queue, each being the owner of multiple tickets in that queue. I created a new custom role, then

Re: [rt-users] Where to put crontool scripts?

Thanks for the thoughts, everyone. I think we'll keep them under local, in their own folder. Good to know upgrading won't touch anything. Sent from my iPhone > On Jan 5, 2017, at 00:54, Alex Vandiver wrote: > > On Wed, 4 Jan 2017 11:13:38 -0500 > Alex Hall

[rt-users] no alert for invalid mail addresses

Hi geeks, sometimes someone here mistypes the mail address of Requestor or CC. The typos in addresses are various, my question is about the really obvious ones. Like if you put to CC an address "a@b". Is there any mechanism in RT to detect such mistakes and say something at least? Or can I have a

Re: [rt-users] How unprivileged users could see all tickets in their queue?

Thanks for your answers. Before work on overlay to custom my rt setup, i have a question. Privileged users have a rights to search in all RT database. But in my setup, some users are customers and they are grouping in RT groups called by their compagny name. On the queues (called by compagny

Re: [rt-users] How to create a new RoleGroup?

Hi, I finally found the problem. Some Upgrade-Script deleted the "AdminCc, Cc, Owner, Requestor"-entries in the column 'name' in the table group. Column updated (the correct entries are also in the column type) and it works. Greetings Patrick     Gesendet: Mittwoch, 04. Januar 2017 um 15:41