Re: [rt-users] Showing tickets for which the user is a CC on the homepage?

2016-09-29 Thread Alex Hall
To be clear, I did try the saved search route. However, I don't know if users can add saved searches so they load right on the homepage without the user first needing to click the right saved search. I've tried to investigate this, but the dashboard builder isn't very accessible, or I have no clue

[rt-users] Showing tickets for which the user is a CC on the homepage?

2016-09-29 Thread Alex Hall
Hi all, Is there any way to get a homepage module to show tickets for whom the current user is a CC watcher? That is, if Alice CCs Bob on a ticket, Bob should be able to see it on his homepage whenever he logs in. He can view the ticket if he goes looking for it, but like unowned or owned by user

Re: [rt-users] DB schema diagrams

2016-09-29 Thread Patrick Muldoon
> On Sep 29, 2016, at 10:37 AM, Matt Zagrabelny wrote: > > On Thu, Sep 29, 2016 at 9:34 AM, wrote: >> Hello, >> >> I'm looking for the schema diagrams for RT 4.2.12, but on the wiki >> (https://rt-wiki.bestpractical.com/wiki/Schema) there are no links for

Re: [rt-users] DB schema diagrams

2016-09-29 Thread Matt Zagrabelny
On Thu, Sep 29, 2016 at 9:34 AM, wrote: > Hello, > > I'm looking for the schema diagrams for RT 4.2.12, but on the wiki > (https://rt-wiki.bestpractical.com/wiki/Schema) there are no links for the > following files : > - Rt schema.svg > - Rt4-schema-relationships.svg > and I

[rt-users] DB schema diagrams

2016-09-29 Thread elifree
Hello, I'm looking for the schema diagrams for RT 4.2.12, but on the wiki (https://rt-wiki.bestpractical.com/wiki/Schema) there are no links for the following files : - Rt schema.svg - Rt4-schema-relationships.svg and I can't find them on our RT. I only find a schema.dot file in the docs

[rt-users] Fw: Aw: Re: REST API; the plus-character (+) will be not processed; plain email

2016-09-29 Thread MDroemer
Dear RT-users, the following solution has been implemented: ... $http({ url: 'http:///REST/1.0/ticket/new', method: "POST", headers: {'Content-Type': 'application/x-www-form-urlencoded; charset=utf-8'}, params: { user: $scope.user, pass: $scope.pass },