Re: [rt-users] Attachments don't reach database for one user

2016-03-25 Thread Chanel Wheeler
That did the trick. Thanks!!

chanel

From: rt-users [mailto:rt-users-boun...@lists.bestpractical.com] On Behalf Of 
Dustin Graves
Sent: Thursday, March 24, 2016 4:49 PM
To: rt-users@lists.bestpractical.com
Subject: Re: [rt-users] Attachments don't reach database for one user

Hi Chanel,

I have tested this locally and it appears to me that all attachments should be 
broken for unprivileged users using the SelfService UI. This is a result of the 
changes made in 4.4.0 to attachments.

I have created a patch for this that appears to fix this problem. You will find 
that patch attached. This will be fixed in 4.4.1.

Thank you,
Dustin

-
RT 4.4 and RTIR Training Sessions https://bestpractical.com/training
* Washington DC - May 23 & 24, 2016


Re: [rt-users] Display custom fields in a ticket

2016-03-25 Thread Joop
On 22-3-2016 23:05, Jeffrey Pilant wrote:
>
> Joop wrote:
>
> >On 22-3-2016 18:56, Jeffrey Pilant wrote:
>
> >> I am a novice at RT.  I was given an instance of RT 3.8.4 to upgrade a
>
> >> while ago.
>
> >> 
>
> >> I upgraded it into RT 4.2.10.  Seemed to be OK.  At least it ran.
>
> >> 
>
> >> Today, months later, I was informed the tickets are not displaying the
>
> >> custom fields that used to be there.
>
> >> 
>
> >> I have confirmed that the field definitions appear to have been copied
>
> >> over.
>
> >> 
>
> >> However, the fields are not showing in the display.
>
> >> 
>
> >> 
>
> >> 
>
> >> Can someone post stuff for me to check?
>
> > 
>
> >Use the Admin part to check if those CF are still 'applied to' your queues.
>
> >Another thing: it could be rights related
>
> > 
>
> >> I suspect it is something as simple as adding the field to the list of
>
> >> things to show on the display page.
>
> >> 
>
> >> However, I don’t know how to do that.
>
> > 
>
> >Its possible some custom code/callbacks did some wonderful things but
>
> >without an idea how it looked like and how its looking now its hard to
>
> >guess as to why it doesn't work.
>
> >Do you happen to have a file backup of the RT install tree?
>
> >That way you can try to find out if any customization has been done.
>
>  
>
> When I check for the custom fields for the queue, I see no fields
> listed under selected and no fields listed under unselected.
>
I just logged into our RT instance to make sure I use the correct terms.
Goto the top menu: Admin/CustomFields/Select
Make sure you have ticket CFs displayed (Only show custom fields for Field)
Select one that is visible in the old system.
Now select 'Applies to' from the top right menu
There it should show you whether that CF is globally visible or only for
selected queues and a list of unselected queues.

Another route would be to select Admin/Queues/Select, select the queue
where your CFs aren't visible anymore and then Select 'Custom Fields'
from the top right menu. That should give you a list of all CFs that are
applicable to that queue.



>  
>
> Just checked my user rights:
>
> My login is a member of the admin group.  The admin group has all but:
>
>   Modify ticket owner on owned tickets [ReassignTicket]
>
>   *Show Articles menu [ShowArticlesMenu]
>
>   Show global templates [ShowGlobalTemplates]
>
>   Show history of public user properties [ShowUserHistory]
>
>   *Allow writing Perl code in templates, scrips, etc [ExecuteCode]
>
>   Create, modify and delete custom fields values
> [AdminCustomFieldValues]
>
> The two with asterisks (*), I pick up via other groups.  So basically,
> I have every right I probably need.
>
>  
>
> Looking at the right of the custom field, it seems to have none.
>
> I think it should have:
>
>   View custom fields [SeeCustomField]
>
> But when I check it and save it, nothing changes on the ticket display.
>
>
You could add a new group add yourself to it and give that group all
rights possible. If the CFs show up than its a rights problem, if they
don't than you have a problem in the database, you can check with
rt-validator.

If you create a new CF does it show up?

Joop

-
RT 4.4 and RTIR Training Sessions https://bestpractical.com/training
* Washington DC - May 23 & 24, 2016


Re: [rt-users] disable url links in ticket history

2016-03-25 Thread Shawn Moore
On 2016年3月25日 at 18:32:36, user1...@qet.be (user1...@qet.be) wrote:
> Hi all,

Hi U,

> Does anyone know if it is possible, or a good way to go to disable the links 
> in the ticket  
> history.
> I clarify:
> We get a lot of tickets where people send us phishing mails they received or 
> mails containing  
> a possible malicious url to analyse.
> What we like to do is implement something that those urls in the history are 
> "not clickable”  
> so that nobody of the first line handlers can incidentally get infected.

The automatic linking in the ticket history is done by a feature called 
MakeClicky. It was designed so that you can add your own parser to augment text 
in other ways too, not limited to just hyperlinking urls (or for that matter, 
“just” hyperlinking). The example in our documentation makes “ticket #xyz” into 
clickable links. But, the way it’s implemented allows you to turn it off 
completely with the following config:

    Set(@Active_MakeClicky, qw());

See https://docs.bestpractical.com/rt/4.4.0/extending/clickable_links.html for 
more information.

> kind regards,
>  
> U

Cheers,
Shawn
-
RT 4.4 and RTIR Training Sessions https://bestpractical.com/training
* Washington DC - May 23 & 24, 2016


[rt-users] disable url links in ticket history

2016-03-25 Thread user1437
Hi all, 

Does anyone know if it is possible, or a good way to go to disable the links in 
the ticket history.
I clarify:
We get a lot of tickets where people send us phishing mails they received or 
mails containing a possible malicious url to analyse.
What we like to do is implement something that those urls in the history are 
"not clickable” so that nobody of the first line handlers can incidentally get 
infected.

kind regards, 

U
-
RT 4.4 and RTIR Training Sessions https://bestpractical.com/training
* Washington DC - May 23 & 24, 2016