agr-rd

Comments

  • We have found a work around on this issue. We have created a status called "create child ticket" and we have a rules that will fire a task to create a child ticket linked to the parent. A simple button to do this would be really helpful. 
  • Another work around until this is created would be to do something like this: 1) Create a ticket status called "Change to Security Techs", "Change to 1st Line Techs", "Change to Desktop Techs", "Change to Server Techs" 2) Create a action rule for each status type to assign the tickets tech group to the appropriate group.…
  • I also am looking for a way to do this. We have about 30 different status types and on any given ticket type Techs need only 2-3 of them.