Great lengthy question that deserves an equality elaborate and well worded answer, kudos. You missed one tiny detail in this 747-sized story.
Is this problem about a single user, or all of them?
Does it happen on one repo, many or all?
Did this problem occur after what version was upgraded to what version?
Is the user logged in?
Can he still login?
Does he get an error message?
Is he granted access to the repo through fisheye/crucible?
Have you sat next to him while trying to exclude user error?
Can you browse the repo?
Have he tried accessing it through another browser?
Is he invited to the review?
Sorry Jonas, I have not used the Atlassian Answers before and I prematurely submitted my question.
We recently performed an upgrade from 3.4.3 to 4.1.1. Afterward, a couple of users have come forward and said they could no longer see reviews from their Review Dashboard. Most users are experiencing no issues.
So, let me answer your questions:
Is this problem about a single user, or all of them? So, far this seems to only affect a couple of users.
Does it happen on one repo, many or all? Again, so far, this only seems to affect a couple of repos and not all users of the repo.
Did this problem occur after what version was upgraded to what version? 3.4.3 to 4.1.1
Is the user logged in? Yes.
Can he still login? Yes.
Does he get an error message? No, the reviews do not show, but all their commits still show up
Is he granted access to the repo through fisheye/crucible? Yes.
Have you sat next to him while trying to exclude user error? No, but I can see that no reviews show up in their Review Dashboard and I can see that Crucible knows about their past review history because it shows in the commit and review statistics from the all users screen for these two users.
Can you browse the repo? Yes.
Have he tried accessing it through another browser? No, but I can have them try that.,
Is he invited to the review? Yes, these were reviews they were invited to review prior to the upgrade.
There are some known issues with upgrades from pre 4.0 version to 4.0.0-4.1.1 (4.1.2 was released recently to make the upgrade experience smoother). Basically it was possible to loose some permissions when mixed case conflicting groups or users were found.
See FishEye 4.1.2 release notes to find more details on those issues: https://confluence.atlassian.com/display/FISHEYE/FishEye+4.1+release+notes#FishEye4.1releasenotes-16August2016-FishEye4.1.2
See also https://confluence.atlassian.com/display/FISHEYE/FishEye+4.1.1+group+name+normalization page to find more details on the issue.
Hope that helps,
I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs