Jeff, That's why I have my scrip put "NOT SET CORRECTLY" in CAPS as a value in the CF. The ticket display will show the CF and the CAPS will STAND OUT and make it easier for the user to see what's up. The Email serves as a reminder to set the CF. Therefore, the user gets reminded two different ways.
Kenn LBNL On Thu, Jan 6, 2011 at 1:57 PM, Christian Loos <[email protected]> wrote: > 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. > > > >
