Comments
-
I'm dealing with this right now...looking daily to see if deployed machines are connected so I can discover them and add them manually...since Orion is unable to import DHCP devices using the discovery tool.
-
I wish creating pollers was easier...I tried creating one, but MIBs and OIDs are way over my head. I have devices that are SNMP enabled, but the universal poller only pulls about 5 fields. Maybe I'm just a helpless novice in SW, but I wish the poller creation tool would just scan for all fields available via SNMP and let…
-
You can do this already by creating a "Bulk Action". Should take you a matter of seconds.
-
I want this for new report requests. "Show me what you want it to look like!"
-
Man! I entered a feature request to somehow identify and REMOVE email signatures from tickets. LOL. I would be able to exclude everything after a particular string.
-
With a good Outlook plugin, this could be an amazing tool in my environment. I don't allow email tickets because I want the user to enter other info to the initial ticket. With a plugin, perhaps it could query the WHD for the appropriate required fields. It may not prevent them from "sending" the email incomplete, but…
-
It seems there are a lot of feature requests for this very same thing (inheriting client from the parent ticket). Strange that WHD singled out a couple of field to prevent this.
-
They can already do this if you gave them permission to "override" the date/time of a tech note.
-
This is a must! I would also love a way to get rid of signatures. Not sure how we'd accomplish something like that...perhaps identify how the string starts, then remove x number of lines after that string. I imagine that would capture many of the images you mentioned as well.
-
+1 I'm also forced to do the same as the OP on a daily basis. I think you just replace the "Myself" option with the dropdown. As long as you're in the dropdown, that option becomes redundant. We don't want to set up a rule based on request type. We want the flexibility to assign tickets ad-hoc. If we were to set up a rule,…
-
Isn't that what the "flagged tickets" functionality is for? Admittedly, I do not use that feature, so I don't know for sure what it does.
-
That clears things up...in that case. I have the same issue...so +1 from me.
-
YES! I'm constantly trying to compare alerts, and having to take screenshots to compare is just annoying.
-
+1...I'd prefer #2.
-
Funny, while you were told it was a bug, I was told that it was a feature request. My child tickets were created from task elements. Perhaps that's the difference. My feature request to them was to allow inheritance of all fields. Not sure why they left a few out...client being one of them. I'll vote for yours.
-
Yeah...it looks a bit XPish...function over form though.
-
+1 I think I have requested something similar in the past. I'm in need of more robust scheduling. I'd like to be able to enter breaks, lunches, different start/end times by day, have the ability to set that schedule up as recurring each week with the ability to overwrite it for a specific day, set up vacations in advance,…
-
Exactly. For the record, the action rule that is triggering the recording of the 1st response time in my case is one which assigns a priority based on other data the user enters in the ticket. This was the best way I could think of to prevent everyone for simply choosing the highest priority for their new report request…
-
I like the idea, but I think it needs additional configuration. What if a different tech responds to your ticket...should the ticket now be assigned to that person? What if another ticket posts the "solution" to your ticket? Should the ticket be assigned to them? I would like to see additional options around your…
-
Pretty sure they make you purchase NPM for that info.
-
What a strange oversight on SolarWinds' part...I just configured my first CAB this week and this didn't cross my mind. My first thought just now was that, maybe for some request types you'd want to give each approver the chance to provide input before denying the ticket, but by second thought was that you could just create…
-
It is a bit of a nuisance, but I've learned to deal with it. Seems strange that it wouldn't be an option though. +1 from me.
-
You would think it would be easy...but it's been requested over and over again and still not done. GET IT TOGETHER SW!!! ;-)
-
Having serial number import automatically would be a lifesaver for me...
-
I would prefer that the ticket number float. I encounter a similar issue when there are a lot of notes in the ticket.
-
typhoon87 In IT...when the ideal solution doesn't exist, you have no choice but to hack it. I agree that this would be a nice built-in feature, but if you scan this site, you'll find hundreds more that think they deserve the same attention...my own included. Since there is no telling when or if this feature will ever be…
-
Adjusting the trigger condition works for me.
-
I have thought about this as well...I would prefer this be taken all the way to separate instances with robust permissions. I'd like to be able to have a customer service department use it to track customer issues, or a maintenance department to track production equipment issues, etc. As of now, each group uses a different…
-
I think that's the intention of the installation date and purchase date fields, though I don't disagree with adding this field for the simple fact that some may use this field for recurring maintenance/support contracts and will tell the user whether the contract is a 1yr, 2yr, etc contract.
-
They replied today that this is by design. Can anyone think of a case where you would want a "system" update to set the 1st response time?