Slush Bucket issue -

[poyntzj]

we have a slush bucket for linking incidents to each other (Incident -> Parent     Note this is not the same as Incident -> Parent Incident)

As admin, it shows all Incidents without a filter needing to be used.

If I go in as a standard process user, the user gets the slush bucket up, but nothing is seen in the left hand window or can be searched

If I change the filter to Active is true and then run the filter, I can then see the active incidents in the left hand window

If I change the filter to Active is false and then run the filter, I do not see any tickets - I suspect this is where it is failing when there is no filter set.

I cannot fathom how this is set or where - i cannot see any Client Scripts set on the Incident table or Task table that would do this (from following another question on slushbuckets and restrictions)

any pointers - clearly not used by too many of our users, but now it has been raised by one I am interested to get it working for them

cheers

[Mike Allen]

The only time I see blank records is if we have blank records.   They are, unfortunately, first alphabetically, so they show at the top and block the user from seeing the actual info I want them to see.

[Kalaiarasan Pus]

guess you are right on this display value might have been blank in my case  

[poyntzj · Accepted solution]

The records are not blank, but the list was just showing   -- None --

I was going to grab a screen shot and now it is working

I did add itil as an edit role earlier and reloaded the form, ran a cache.do and it did not have an impact

now it has.

that would explain why I could not find a Dictionary entry too

[UPASANA2]

Hi Julian,

Could you please elaborate your answer, even we are facing the same issue. Where did you add itil as an edit role and why did you execute cache.do? Did it solve the issue?

[poyntzj]

Yeah, it worked fine after that

I have had a similar problem before with a form corruption that was annoying me.

when Servicenow looked it was fine and I was advised to try a cache.do

that worked then so I do it every so often if things seem not to be behaving as I expect