"Affected User CI" Auto-Populates with "Users" Primary Assigned Asset.
Adrian_Paech
Customer Advanced IT Monkey ✭✭✭
Essentially the same functionality as the Console (where it auto-looks up the user's primary Asset) and populates it in a drop down box to be quickly added as a related CI.
This is actually the main feature preventing us from using the portal across the board, as our first level analysts require this feature all the time.
1
Best Answers
-
Geoff_Ross
Cireson Consultant O.G.
Adrian, if I understand what you mean, we have this functionality already. At the bottom of the incident form, you will see the Affected Configuration Items section which has two 'Add' controls. the left hand one if the Generic Config Item picker (to pick any CI in the system) but the right hand one is the Affected User's Items drop down.
5 -
Joe_Burrows
Cireson Devops Super IT Monkey ✭✭✭✭✭
I see we had a bug for it fixed in 5.0.4 (see https://support.cireson.com/KnowledgeBase/View/1306#/) – may pay to apply the latest hotfixes. Let me know if this fixes the issue and ill convert this from a feature request to a question.
5
This discussion has been closed.
Answers
Not sure why but the Affected User Items Drop Down box is always blank for us, even when you click on the "drop down", its like it tries to populate, but nothing appears.
However, if I open up the same call ( / affected user) in the console, I can see Affected User CI drop down box auto-pupulate with the correct CI.
Seems like it should work (and pre-populate), but it does not seem to?
Is there a fix or special configuration for this to work?
Regards,
Adrian
I see we had a bug for it fixed in 5.0.4 (see https://support.cireson.com/KnowledgeBase/View/1306#/) – may pay to apply the latest hotfixes. Let me know if this fixes the issue and ill convert this from a feature request to a question.
Thanks again!