When a group member is no longer part of a Group Requirement Type data view, the group member still shows as having that requirement met even though they do not belong to the requirement data view any longer.
Group Member in Group Showing that Requirement has been met:
Actual Behavior
A group member initially met one of the group requirements, however, the birthdate was updated which caused the group member to no longer be part of the data view associated with the requirement. After the Calculate Group Requirements job was run, Refresh Requirements was clicked within this group member's detail, but it still shows that the specific requirement has been met.
Dataview that the Requirement is referencing:
Group Type Role with Requirement:
Dataview Filters:
Group Member that does NOT meet requirement:
Live Scan/Background Check is NO
Person is older than 12:
Group Member NOT in Dataview:
Group Member Detail in Group Showing that Requirement has been met:
Expected Behavior
When this group member was no longer part of the Group Requirement Type data view, that group member's requirement should've shown as not being met within the group member details.
When testing this on our demo site (currently 16.5) the group member that no longer met the requirements showed as 'not met' after the Calculate Group requirements job ran.
Steps to Reproduce
Create a dataview and link to a group requirement type.
Add requirement at the group type level to the specific group role.
Find a person in a group of that group type who is also in a group requirement data view.
Update the person so that they no longer meet one of the requirements.
Check the requirement data view to make sure they are no longer there.
Click into the group member's detail from the group and click 'Refresh Requirements.'
Issue Confirmation
[X] Perform a search on the Github Issues to see if your bug or enhancement is already reported.
[X] Reproduced the problem on a fresh install or on the demo site.
Description
When a group member is no longer part of a Group Requirement Type data view, the group member still shows as having that requirement met even though they do not belong to the requirement data view any longer.
Group Member in Group Showing that Requirement has been met:
Actual Behavior
A group member initially met one of the group requirements, however, the birthdate was updated which caused the group member to no longer be part of the data view associated with the requirement. After the Calculate Group Requirements job was run, Refresh Requirements was clicked within this group member's detail, but it still shows that the specific requirement has been met.
Dataview that the Requirement is referencing:
Group Type Role with Requirement:
Dataview Filters:
Group Member that does NOT meet requirement: Live Scan/Background Check is NO
Person is older than 12:
Group Member NOT in Dataview:
Group Member Detail in Group Showing that Requirement has been met:
Expected Behavior
When this group member was no longer part of the Group Requirement Type data view, that group member's requirement should've shown as not being met within the group member details.
When testing this on our demo site (currently 16.5) the group member that no longer met the requirements showed as 'not met' after the Calculate Group requirements job ran.
Steps to Reproduce
Issue Confirmation
Rock Version
16.6
Client Culture Setting
en-US