billy.ellison

Not having this is proving crippling. Now end users will end up having to double and triple key information without this option. It can't come soon enough!

Thanks Billy. I'll check it out and see if we can somehow massage this data into a usable format.

Using a custom field negates all timers in the system however. Unfortunate

Thanks, that is what I was afraid of. I offered that as an option too for Brands, but the powers that be didn't like that option. They wanted them to think Brand from the very beginning.

As kellytice‌ mentioned, it is not currently possible. I have a similar situation that would make our workflow much more user friendly. This feature request is available to vote for as well. You can vote here.

We ended up running on a Windows 2012 R2 server just from a best practices scenario for our utilization. Yes, I think in general we would like to run a pure Linux environment, but Windows has pretty well suited us to this point. Getting ready to add 30 more techs, though, so we'll see if that still continues to hold true.

+1 for this. We are muddling through it now, and have some of it figured out, but actual layout documentation for reporting would be great!

reply.prak Can't speak as to recommended or best practice, but we have done this exact setup on a SQL2012 server, and have not seen any noticeable performance issues at this point. If you have a NetFlow database, that's another story, but NPM and WHD seem to be playing together fine in our environment.

Not an exact answer to your question, but we have encountered similar difficulty. Based on subject lines and From email addresses, we have been able to do some routing using Action Rules and Processes, but not actual data manipulation. Conceptually, you could use the API to read in the details of new tickets and re-push…