Analyst Archive Access Problem
Riddle Me This Batman. I have ONE Analyst. He can access any IR, SR or CR in the Archive… EXCEPT his own CRs! He can pull up anybody else's CRs, just not his own. I check for scoped access, couldn't find any. Checked Security, nothing. Checked profile, nothing found. I don't know where to look.
Thanks for any clues or insights.
Answers
@Brian_Winter I created an Incident for this issue this week ;) This seems to be a problem with the AssignedTo property. CreatedBy is not a problem, but it is not possible for users to open change requests form the archive where they are the assignedto users.
Do you also get the following error in the console?
Why yes I do! What makes this one (so far) user so unlucky? I can't find anything different in the CI$User or elsewhere that stands out.
@Brian_Winter we have this issue with EVERY analyst. No analyst is able to open CRs where he/she is tje assignedto user from the archive.
In your case, are all other analysts able to open their changes?
For us, it's just one guy. Everybody else has no problems.
Hi @Brian_Winter,
When this user attempts to open one of these CRs, is the browser hanging with the dots and throwing JavaScript errors in the browser console, or are they getting the message that the ticket is not accessible?
@Simon_Zeinhofer I tried to replicate the problem in my lab without success. The issue in your case is that console is expecting the pageForm.viewModel object to be a Kendo Observable and this does not appear to be the case in your environment. The error suggests that pageForm.viewModel is being redefined as a simple JS Object at some point. I would look through the custom code to check that nothing is redefining the pageForm.
@john_doyle Thanks for the information ;)
But why does this only affect changes from the archive where I am the AssignedTo user? I can open every other change from the archive. And I thought Custom Code is not executed on Closed Work Items and Work Items from the Archive?
@Simon_Zeinhofer I have to assume that some code is running when the assigned to user is matches the current user. Without seeing all your custom code I can't say what it could be. A search in the CustomSpace folder for files containing the work 'AssignedWorkItem' may reveal what is happening.
Hi guys,
We're seeing about 80% of the time a white screen and the rest of the time the spinning dots of wait forever. We see the JS script errors shown above. One lucky guy, nobody else. I was thinking browser settings until he tried all his browsers and different machines, so now it's pointing to his account access.
@john_doyle I couldn't find any customization which uses the AssignedWorkItem property in the code :/
hm…seems like some fun searching for the reason of this behaviour :D
@john_doyle i deactivated our whole custom.js and still I cannot open any changes from the archive, where i am the AssignedTo - in our test system it works.
Might it be that a class extension leads to this behavior?