Re: [rt-users] Projects grouping
Would a gantt chart do? There's RT::Extension::JSGantt: https://metacpan.org/pod/RT::Extension::JSGantt I think its better than Jira's projects page because that page is Jira is too noisy. There is a screen grab on bps' extensions page: https://www.bestpractical.com/rt/extensions.html And then you can make a projects index with a dashboard/saved search with the following TicketSQL: Queue = 'Projects' AND HasMember IS NOT NULL AND ( Status = 'new' OR Status = 'open' ) On 5/23/15 8:10 AM, Darin Perusich wrote: I'd like to be able to classify a group a tickets, mark them as a project, and have that project be accessible under a Projects menu available along the top of the RT interface which I can then select and display only those tickets. For those that have used Jira I'm basically looking to mimic, to an extent, how Projects are treated/displayed in their ServiceDesk offering. I realize I could create additional queues to facilitate this behaviour, however I do not want the overhead associated with creating new queues, and want these tickets to live under an existing queue. I didn't see any existing extensions which provide this functionality and am curious to know if anyone has wanted this behaviour and how they've addressed it. Also, if this is something Best Practical has implemented or has thoughts on I'd be interested in engaging them for some custom development.
[rt-users] Projects grouping
Hello All, I'd like to be able to classify a group a tickets, mark them as a project, and have that project be accessible under a Projects menu available along the top of the RT interface which I can then select and display only those tickets. For those that have used Jira I'm basically looking to mimic, to an extent, how Projects are treated/displayed in their ServiceDesk offering. I realize I could create additional queues to facilitate this behaviour, however I do not want the overhead associated with creating new queues, and want these tickets to live under an existing queue. I didn't see any existing extensions which provide this functionality and am curious to know if anyone has wanted this behaviour and how they've addressed it. Also, if this is something Best Practical has implemented or has thoughts on I'd be interested in engaging them for some custom development. Thanks! -- Later, Darin
Re: [rt-users] Projects grouping
On 23-5-2015 14:10, Darin Perusich wrote: Hello All, I'd like to be able to classify a group a tickets, mark them as a project, and have that project be accessible under a Projects menu available along the top of the RT interface which I can then select and display only those tickets. For those that have used Jira I'm basically looking to mimic, to an extent, how Projects are treated/displayed in their ServiceDesk offering. I realize I could create additional queues to facilitate this behaviour, however I do not want the overhead associated with creating new queues, and want these tickets to live under an existing queue. I didn't see any existing extensions which provide this functionality and am curious to know if anyone has wanted this behaviour and how they've addressed it. Also, if this is something Best Practical has implemented or has thoughts on I'd be interested in engaging them for some custom development. Maybe the bookmark functionality can be used for this? It allows for any ticket to be marked and displayed by the bookmark portlet. Let us know if you manage to come up with something usable, its a nice idea. Regards, Joop
Re: [rt-users] rt-crontool not sending mail, no errors
Hi Fredrik, Have you tried using a simpler BeforeDue condition to test? Something like --condition-arg 2h. I don't think you need to specify the 0d, and it may confuse the condition module. You can also try to modify the search to return something very specific (search by ticket id for example) so that you can verify that the --action part works properly. I have similar notifications for Reminders working with the following command, just in case it's useful: /opt/rt4/bin/rt-crontool \ --search RT::Search::FromSQL \ --search-arg 'Type = reminder and (Status = open or Status = new) and Due now' \ --condition RT::Condition::BeforeDue \ --condition-arg 5m \ --action RT::Action::Notify \ --action-arg Owner,AlwaysNotifyActor \ --transaction first \ --template 'Reminder' Regards. 2015-05-22 13:03 GMT+02:00 Fredrik Nyström fredrik.nyst...@prevas.se: Hi, I'm trying to use rt-crontool, to send out reminders when a ticket expires due date. The command and output is like this, but no mail is sent: [root@server ~]# /opt/rt4/bin/rt-crontool --search RT::Search::FromSQL \ --search-arg 'Queue = The Queue and (Status = open or Status = new)' \ --condition RT::Condition::BeforeDue \ --condition-arg 0d2h3m1s \ --action RT::Action::NotifyGroup \ --action-arg 'm...@domain.se' \ --transaction first \ --template 'Reminder due soon' \ --verbose \ --log debug [3011] [Wed May 20 06:53:26 2015] [debug]: The RTAddressRegexp option is not set in the config. Not setting this option results in additional SQL queries to check whether each address belongs to RT or not. It is especially important to set this option if RT recieves emails on addresses that are not in the database or config. (/opt/rt4/bin/../lib/RT/Config.pm:505) 18079: Using transaction #111037... 18331: Using transaction #113770... Does anyone know, what could be the problem here? And, yes, mailing works, when you for exapmle resolve a ticket from the web interface. BR Fredrik
