Skip to content

Commit f31eed6

Browse files
committed
add configurable slas documentation [tarot-3323]
1 parent 3da6bad commit f31eed6

3 files changed

Lines changed: 16 additions & 4 deletions

File tree

108 KB
Loading
105 KB
Loading

docs/organizations/managing-security-and-risk.md

Lines changed: 16 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -225,10 +225,7 @@ Codacy closes a finding when it's not detected in a subsequent DAST report. If a
225225

226226
## Finding severities and deadlines {: id="item-severities-and-deadlines"}
227227

228-
!!! note
229-
Currently, Codacy doesn't support customizing the severity rules for security findings.
230-
231-
The following table defines finding severities and the number of days to the deadline to fix the associated security issue, based on the importance of the underlying issue:
228+
The following table defines finding severities and the default number of days to the deadline to fix the associated security issue, based on the importance of the underlying issue:
232229

233230
| Finding<br/>severity | <br/>Days to deadline | Underlying Codacy<br/>issue severity | Underlying Jira<br/>issue priority <sup>1</sup> |
234231
|----------------------|-----------------------|--------------------------------------|-------------------------------------------------|
@@ -239,6 +236,21 @@ The following table defines finding severities and the number of days to the dea
239236

240237
<small><sup>1</sup> Those listed are the default Jira priority names. If you rename a default Jira priority, it keeps the correct mapping.</small>
241238

239+
### Customize deadlines {: id="item-configurable-deadlines"}
240+
241+
!!! info "This feature is available only to [organization admins and organization managers](../organizations/roles-and-permissions-for-organizations.md)."
242+
243+
You can configure your findings deadline clicking on the "Configure SLAs" button, on the right corner of the page.
244+
245+
![Security and risk management SLAs configure](images/security-risk-management-slas-configure.png)
246+
247+
By opening the configuration modal, you'll be able to input your deadline preferences for each severity. Each deadline requires at least 1 day and can't exceed the maximum of 9999 days to be solved.
248+
249+
![Security and risk management SLAs configuration modal](images/security-risk-management-slas-modal.png)
250+
251+
As soon as changes are saved, your findings statuses will be updated accordingly, whether they are opened or closed.
252+
You are also able to reset to Codacy default deadline values (see table above) at any time.
253+
242254
## Finding statuses {: id="item-statuses"}
243255

244256
The following table describes how finding statuses map to deadlines:

0 commit comments

Comments
 (0)