Help Desk Software & Beyond
May 17, 2012, 04:03:43 AM *
Welcome, Guest. Please login or register.
To post messages you need to register. We apologize for inconvenience, but this is to prevent spam.
Registration is instant (no email verification) and we do not ask for any personal information.

Login with username, password and session length
News: Welcome to Help Desk Software forum!
 
   Home   Help Search Login Register  
Pages: [1]
  Print  
Author Topic: [REQ] Undocumented options - "claimnotice=1"  (Read 1860 times)
ihiebert
Newbie
*

Karma: 0
Posts: 12


View Profile
« on: March 30, 2010, 12:50:13 PM »

We are using 3.01  and added the "claimnotice=1" option, but the notification only goes to the operators, we would like it to go to the user as well - (so they know the ticket has been picked up)

Edit by Sparky-  Please follow posting guidelines in sticky threads.  Title fixed.
« Last Edit: March 30, 2010, 01:09:19 PM by ihiebert » Logged
Sparky
Moderator
Hero Member
*****

Karma: 83
Posts: 2,228


stop pushing all those buttons


View Profile
« Reply #1 on: March 30, 2010, 01:06:40 PM »

We are using 3.01  and added the "claimed=1" option...

There is no "claimed=1" in the undocumented options thread so that may be part of the problem.
« Last Edit: March 30, 2010, 03:49:49 PM by Sparky » Logged

Did you update the paths in ttxcfg.cgi after moving TTX to your new location?   Undecided
To those seeking help.... please report back when you figure it out.  Cheesy
ihiebert
Newbie
*

Karma: 0
Posts: 12


View Profile
« Reply #2 on: March 30, 2010, 01:11:22 PM »

Sorry, I meant "claimnotice=1" - Sends a notification email when ticket is claimed

(I am by myself today and getting hammered by tickets and impatient users asking if I received their ticket or not - )
Logged
Sparky
Moderator
Hero Member
*****

Karma: 83
Posts: 2,228


stop pushing all those buttons


View Profile
« Reply #3 on: March 30, 2010, 01:16:42 PM »

Sorry, I meant "claimnotice=1" - Sends a notification email when ticket is claimed

(I am by myself today and getting hammered by tickets and impatient users asking if I received their ticket or not - )


This item is still included in version 3.

Have you tried it yourself as a customer?
Logged

Did you update the paths in ttxcfg.cgi after moving TTX to your new location?   Undecided
To those seeking help.... please report back when you figure it out.  Cheesy
ihiebert
Newbie
*

Karma: 0
Posts: 12


View Profile
« Reply #4 on: March 30, 2010, 01:57:13 PM »

Yes, and the claimed notification only goes to the operators, which may be the intended function, but I was hoping there was a way to set it so that the claimed notification goes to both the operators & the user.
Logged
Sparky
Moderator
Hero Member
*****

Karma: 83
Posts: 2,228


stop pushing all those buttons


View Profile
« Reply #5 on: March 30, 2010, 02:14:43 PM »

TTXTicket.pm, claim subroutine.  Remove the red and add the blue.

This is untested so let me know if it works.  Supposed to remove claim notification to operators and send to customer.

Quote
  unlockdb();
  if ($notify) {
    my @oplist = TTXUser::list();
    if ($usewrkh eq undef) {
      eval 'use TTXWorkHours';
      $usewrkh = 1 if $@ eq undef;
    }
    foreach my $o (@oplist) {
      my $u = TTXUser->new($o);
      next if $u eq undef || $u->{email} eq undef || ($usewrkh && !TTXWorkHours::onguard($u->{wrkh}));
      TTXMail::sendmail(
        {
          to => $u->{email}
          to => $t->{email}
          from => '"'.company($cfg, $t).'" <'.$cfg->get('email').'>',
          subject => 'Notice: ticket '.$t->{id}.' claimed by '.$t->{oper},
          msg => 'Notice: ticket '.$t->{id}.' claimed by '.$t->{oper}."\n\n".
                 "This is a notification only, please do not reply to this message\n"
         }
       );
     }
  }
  return 'ticket';
}
Logged

Did you update the paths in ttxcfg.cgi after moving TTX to your new location?   Undecided
To those seeking help.... please report back when you figure it out.  Cheesy
ihiebert
Newbie
*

Karma: 0
Posts: 12


View Profile
« Reply #6 on: March 30, 2010, 03:01:39 PM »

no change, Claimed notification still went to operator only. (it looked like it should have worked though ?)
Logged
Sparky
Moderator
Hero Member
*****

Karma: 83
Posts: 2,228


stop pushing all those buttons


View Profile
« Reply #7 on: March 30, 2010, 03:39:09 PM »

no change, Claimed notification still went to operator only. (it looked like it should have worked though ?)

Now that makes no sense.

$u->{email} is the Operator's email address.

$t->{email} is the email address for the ticket (belongs to the customer).

How did you make the edits?  On your hard drive, then upload? (best) Or did you edit via FTP? (not so good)

Look and make sure the edits were accepted into the file.
Logged

Did you update the paths in ttxcfg.cgi after moving TTX to your new location?   Undecided
To those seeking help.... please report back when you figure it out.  Cheesy
ihiebert
Newbie
*

Karma: 0
Posts: 12


View Profile
« Reply #8 on: March 30, 2010, 03:49:16 PM »

No, I did something really basic, I uploaded the backup file (original) instead of the new modded one.

Tested & works great !

Thank you very much for your help !
Logged
robwellesley
Jr. Member
**

Karma: 3
Posts: 53


View Profile
« Reply #9 on: April 20, 2010, 06:30:17 PM »

would adding

 cc => $u->{email}

allow for both?
Logged
Sparky
Moderator
Hero Member
*****

Karma: 83
Posts: 2,228


stop pushing all those buttons


View Profile
« Reply #10 on: April 20, 2010, 06:49:52 PM »

would adding

 cc => $u->{email}

allow for both?

No.

Reference my Cc: mod... simply getting a Cc: to operate requires a whole bunch of other edits.
Logged

Did you update the paths in ttxcfg.cgi after moving TTX to your new location?   Undecided
To those seeking help.... please report back when you figure it out.  Cheesy
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1 RC3 | SMF © 2001-2006, Lewis Media Valid XHTML 1.0! Valid CSS!
Page created in 0.028 seconds with 19 queries.