The most recent content from our members.
Please. Please. PLEASE. Creating dependencies is pretty clunky at the moment. It would be super neat if we could enable automatic dependency mapping for specific nodes, instead of having to choose between all or nothing. Improved dependency creation has huge potential for SolarWinds. Right now I have over 400 500 600 700…
I would like a way to hide child assets from clients so that they do not see bombardment of data that they do not need when submitting tickets this would enable us to more effectively use the ability of the WHD to manage and track software. Currently if a child asset is assigned to a user, the end user see's that child…
I’ve been told it isn’t supported by Orion. True parent / child relationships would allow you to properly suppress alerts. For instance, if a switch (Parent) goes down, all the servers (children) hanging off that switch are going to be down, and being informed about the 20+ servers along with being notified the switch is…
When an interface goes down on a server I want the parent object to be in the warning status. Currently I have the "Show child objects also" checked on the parent object it shows a red dot next to the parent object, but doesn't bring it up to the two parent maps. Currently I have the "Status Rollup Mode" set at default…
I have an onboarding workflow where Child Tickets get created. I would like to be included on the ticket given to one of our Techs who is responsible for setting up the IP Phone. I need to know the IP Phone extension so I can update AD, so if I could be included (CC'd) on the child ticket, he could enter the phone…
I was watching a SolarWinds YouTube video where they show how to create a parent-child relationship using Action Rules. About 5 minutes into the video, it shows a child ticket and the child ticket has a Client associated. How is that done? All my child tickets have Nothing in the Client field. I would like my child tickets…
I know this has been brought up a few times in a few different ways but I think it's worth repeating or presenting in another way... Business case/use scenario: * Client submits a ticket for a new account * There are 3 different tech groups that need to touch the ticket* The Service Desk which owns the main account…
We have created a child/linked ticket, creating an automatic ticket to the SCCM team when the AD team creates a "Delete from AD" ticket. The problem is that the child ticket is not inheriting the asset number, even though the box is checked to do so. Anyone else seen this behavior? Kim
Wondering why the decision was made to NOT include the Description contents in a Child Ticket. When we create a workflow and child tickets are created, it seems that about 99.9% of the time, having access to the Description contents would be beneficial to the tech who has the Child Ticket. Since techs have access to click…
If you don't have groups set up to create dependencies its a little annoying to have to create a tiny group just to put behind one parent node. It would be nice if we could, in the event we can't justify making a group for 2-3 nodes, select multiple nodes as children w/o having to create a group for them, Thanks!
It looks like you're new here. Sign in or register to get started.