How about put a comment with your script in the ticket. The Ticket history would then look like this: * Status change from open to resolve * Comment: ERROR: Cannot resolve without a value for BlahBlah. * Status change from resolved to open
I think this would make it clear for the user why they can't resolve the ticket. -Chris Am 06.01.2011 19:10, schrieb Jeff Blaine: > As part of my current solution (ongoing) to the "Don't allow > resolve if a certain CF is not set" topic, I am resetting > the ticket status back to "open" when I see that someone > tried to resolve while the specific CF was not set. > > Unfortunately, even though my code set the status back to > "open", the "BriefMessage" on the transaction still says > that the status went from "open to resolved" ... yet the > ticket shows properly *as open still*. > > Is there a way to queue one of these notices to the user > from within my Scrip? > > ERROR: Cannot resolve without a value for BlahBlah. >
