To support issue tracker integrations, Software Risk Manager will make requests to the issue tracker server periodically in order to create, update, and read issues. Due to the volume of requests that can be made in quick succession, issue tracker servers may begin to deny requests to prevent the server from being overloaded.
The following properties will affect how Software Risk Manager makes requests.
azure.auto-create-delay[default: 50] - sets the delay (in ms) between subsequent work item creation requests made during an auto create job.gitlab.auto-create-delay[default: 60] - sets the delay (in ms) between subsequent requests made during auto create jobs and bulk update jobs.jira.auto-create-delay[default: 50 - sets the delay (in ms) between subsequent issue creation requests made during an auto create job.servicenow.request-delay[default: 750] - sets the delay (in ms) between subsequent requests made during auto create jobs and bulk update jobs.
It is also possible to configure result and finding level data that SRM includes when querying issue tracker data and in the issue tracker sync process.
The following properties will affect what data Software Risk Manager includes when querying issue tracker data.
issuetracker.include-archived-results[default: true] - if false, result data will not include archived results.issuetracker.include-gone-in-active-findings-group[default: true] - if false, result data will not include Gone findings if an active version of the same finding also exists. If all findings in a group linked to an issue are Gone however, the group will be considered Gone and all the Gone findings included. This property only ignores Gone findings when at least one non-Gone finding is present in the group.