Why would the Assignment Rule field in the VIT be empty if it has been assigned by a rule?

[benevans]

 I'm trying to get an explanation why some of the data we are seeing on Vulnerable Items table is as it is.

For example, when we look at the Vulnerable Items table, we see something like this:

Look at the 3 right-most values (Assignment Group, Assignment Rule, Assignment Type) .  Notice that even though Assignment Type = 'Rule' and Assignment Group = 'DIT-PEDS-VR' the Assignment Rule that determined the Assignment Group remains empty.  The Assignment Group is correct according to the rules that we currently have active, but the rule that is actually making the assignment is not shown.

If I actually go to VIT0862269 for example, I can look at the work notes and see what looks like a reasonable sequence of activities that have occurred:

I can understand the work notes where the original VIT was closed, then was opened again, first with one risk score, then with an upgraded risk score, and subsequently was assigned to the appropriate Assignment Group.  I just have not been able to determine why Assignment Rule in the list view is empty.

I think I understand that even though some criteria may change, once the actual Assignment Group has been selected, that selection would not change to prevent work assignments from being thrashed around, but why would the rule that caused the assignment in the first place be cleared out?

Any clarification that could be provided regarding this would be appreciated.

[Martin Dewit]

One thing right off the bat - you should probably be careful with what links you post ('DIT-PEDS-VR ') and what your screenshots contain especially around such a sensitive subject (vulnerability management).

Can you verify in your ARs that there is indeed an applicable assignment rule? You could also try to Reapply in the VM workspace (or USEM) to see if that populates your assignment rule. Whenever I face unusual issues like this my first course of action is to update the apps to the most recent version. There could be a defect or known issue with the current version you are on.

[benevans]

I updated the app on 7/14 and reapplied the rules, but it didn't seem to make any difference.

I should have included this history screenshot in my original post.

It shows where the assignment rule is set on 6/23, then is wiped out on 6/24.  That's what I don't understand.