Vuln2jira implements Deming Cycle paradigm. Following four steps are executed at every application run:

For each host with existing vulnerabilities (according to filters set in configuration) JIRA issue is created. It contains:
If vulnerability was found for existing issue with status “Closed” change is made automatically to “Reopened”. Also if vulnerabilities exist for “Resolved” issue, change is made to “Reopened”. Automatically another CSV attachment is created, “Description” field is updated and new comment about changes in vulnerabilities list appear. For issues with no existing vulnerabilities status is automatically changed to “Closed”.
For every vulnerability found according to filter set in vuln2jira issue is automatically created in this mode. Issues’ closing and reopening is managed by the program. This mode is recommended for well patched systems only (with relatively small number of vulnerabilities). Otherwise huge number of issues may saturate JIRA and affect the performance.
If vulnerability was found for existing issue with status “Closed” change is made automatically to “Reopened”. Also if vulnerabilities exist for “Resolved” issue, change is made to “Reopened”. Automatically “Description” field is updated and new comment about changes in vulnerabilities list appear.
For issues with no existing vulnerabilities status is automatically changed to “Closed”.
Plugin “Accept Risk Add-on” is available for purchase. It extends functionality of vuln2jira by enabling registering AcceptRisk request in Security Center from JIRA.