Re: [rt-users] Limiting rt-crontool notifications to every n days?

On Tue, Jan 17, 2017 at 1:24 PM, Alex Hall wrote: > Did your JSON-like syntax for > updating fields ever make it into core for 4.4.1? Not yet. -m

Re: [rt-users] Limiting rt-crontool notifications to every n days?

Just download the .bin and move it into /opt/rt4/lib/RT/Action/ModifyCustomField.pm -m On Tue, Jan 17, 2017 at 1:24 PM, Alex Hall wrote: > Thank you, that looks like it'll work. Did your JSON-like syntax for > updating fields ever make it into core for 4.4.1? I found the

Re: [rt-users] Limiting rt-crontool notifications to every n days?

Thank you, that looks like it'll work. Did your JSON-like syntax for updating fields ever make it into core for 4.4.1? I found the attachment in your linked message, but it's a bin file and I'm not sure what to do with it. On Tue, Jan 17, 2017 at 11:17 AM, Matt Zagrabelny

Re: [rt-users] When replying to a new ticket a new ticket get created

Well i have looked at the rights. I have created a group called support and gave all the necessary access and for the group All in general rights i gave them access to everything, comment, register new tickets, create tickets and so on. Really strange, anyone have any more ideas? Martin

Re: [rt-users] Limiting rt-crontool notifications to every n days?

Hey Alex, On Mon, Jan 16, 2017 at 8:18 AM, Alex Hall wrote: > Hi all, > RT is sending out notifications for old tickets just like we want it to. If > a ticket hasn't been updated in seven days and the status is open or new, > the owner gets an email every weekday until the

[rt-users] REST-API crashes on history of long ticket with long format

Hi everyone, I have a ticket with a long history and many merges, but it shows fine under /rt/Ticket/History.html?id=$ID. RT also gives me its history without problems when I use the REST-API with the short format /rt/REST/1.0/ticket/$ID/history -> RT/4.2.12 200 Ok # 642/642 (/total) [...]