Bug - policy view modal does not display correctly reviewer information

We have a policy called “Development Rules” — Policy Reviewer Contact is a group called “Development Group”.

“Development Group” contained exactly 1 user, the old head of development.

When this user reviewed this policy, the history / changelog showed his name. This was great.

Now we have a new head of development, so I kicked the old user out of this group and added the new one.

The result was that all old reviews now show the name of the new head of development, thus my changelog history is screwed.

Is this a bug? This definitely should not happen, I need the changelog history as evidence.

See? All the changelog history was changed, dating back to 2021. The “U” user I have masked here is the new guy who just started.

@j.meyer

1 Like

Have the same behavior … if I have two people in the group it will be shown both … even if only one had done the review.

Damn, you are right, I hadn’t even noticed that. I wrongly assumed it would only show the one person who actually did the review.

Anyway, so we now have two points to be addressed here, thanks for pointing the additional issue out.

On e3.24.1:

there is the bug mentioned by @Ovidiu:

  • create group A and B in eramba
  • create user account A and B, assign A to group-A and B to group B
  • create a policy as admin where the owner is A and the reviewer is B
  • if you “View” the policy you see the following:

  • now add account A to group B
  • complete the review which is incomplete (as admin user) and save

  • if you view the policy, you will see the following which is ok

  • now remove both users from group B, leaving the group empty

  • complete again the missing review record as admin

  • view the policy and you will see the following. this should have shown the same as before (when we did the view) and on the last review, were group B was empty, you can display “group b - no user accounts in the group”

Int. ref.: https://github.com/eramba/eramba/issues/5061

Thanks for confirming that this is not desired behaviour.

thx, can we have a rough timeline when the bug will be fixed? short term … midterm … longterm?

Short-term, we hope to include it in 3.26.0.

Awesome, I hope there is a way to fix the mess that resulted as my changelog history now shows somebody reviewed policies before he even started working here.