Hello community,
I'm currently implementing the Vulnerability Response Integration with Atlassian Jira integration for a customer. however I'm facing a rather bothering issue when it comes to state mapping.
Within the ServiceNow platform, we have put False positive and Exception request approval rules in place, which as standard, update the Remediation tasks state to: In review / Closed / deferred accordingly.
As per the Agile tool state mapping('sn_vul_agile_tool_state_mapping') : The state will only be synchronised from ServiceNow to Agile tool if the entity state is Closed in ServiceNow or if any entity is Reopened (i.e. State is Open). All other states will be reflected from Agile tool to ServiceNow.
Therefore, this is resulting in a flapping scenarios where:
- ServiceNow's Remediation task is moved to In review (pending approval)
Jira is overriding this state, and moving us back to a previous state, meaning that we lose visibility over the approval request
- OR in the event that ServiceNow validate an exception request:
- ServiceNow's Remediation task is moved to Deferred (exception)
Jira again overrides this state and moves us back to the previous state, losing visibility and tracking of the exceptions that have been approved
I'd appreciate any feedback on this issue, and what steps you may have taken to avoid this flapping? It appears to be the 'intended' logic of the integration but it seems flawed.
