Lou
I've been an administrator for 4 years, specializing in business rules.
-
Total activity316
-
Last activity
-
Member since
-
Following0 users
-
Followed by2 users
-
Votes83
-
Subscriptions98
Comments
Recent activity by Lou-
Paul Toomey The down side to that is you're limited to 100 tickets at a time. We have many problem tickets with well over 100 linked tickets.
-
I have also confirmed that this only happens when I run the macro while bulk updating tickets. If I run the macro on a single ticket, no problem.
-
My password was wrong. It's working now. Here's the extension: As far as the trigger, it's just the action you need to see:
-
Actually, mine's been failing. I'll need to open a ticket to see what's going on.
-
I verified the issue exists in Chrome, Firefox and MS Edge. It also existed in Chrome incognito. I have also confirmed the issue in Chrome with ?noapps invoked.
-
I have NEVER had a successful test on a target. Don't know why that doesn't work. You'll just have to test it out live, preferably in your sandbox.
-
That's it. You can also send public replies by changing the target to [public]=true. I like this better than "notifying" the customer because it is then documented in the ticket. Also, the trigger ...
-
I'll have to wait for another example to pop up. In the meantime, it does appear this only happens when running the macro while bulk editing tickets, although I may be mistaken on that.
-
Again, it is a macro that sets the subject, well after the ticket is created. When the macro is run, those values DO exist.
-
Also, it's not just org fields. It appears to be happening with any placeholder. I have the same thing going on with ticket field placeholders.