From what I understand: Vulnerabilities which are deferred using an exception rule, if they close and then open whilst deferred no longer retain the deferred status and move to open.
I believe from reading the forums this is as designed and there is another question someone posed here which indicated this is as intended: https://community.servicenow.com/community?id=community_question&sys_id=7c2ba2c3db090d10dd886c8e1396...
And a linked feature request which I have upvoted.
However I still have an issue where the business is expecting these vulnerabilities to remain deferred even when they re-open until the deferral end date. Has anyone else experienced this and has anyone come up with a workaround to meet the business expectation? (eg, is there a script/rule/configuration we can change to work around this problem?)
