diff options
Diffstat (limited to 'server/sonar-docs/src/pages/user-guide/issues.md')
| -rw-r--r-- | server/sonar-docs/src/pages/user-guide/issues.md | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/server/sonar-docs/src/pages/user-guide/issues.md b/server/sonar-docs/src/pages/user-guide/issues.md index 63b322cbb1e..440adcfda72 100644 --- a/server/sonar-docs/src/pages/user-guide/issues.md +++ b/server/sonar-docs/src/pages/user-guide/issues.md @@ -37,6 +37,8 @@ Sometimes, issues are self-evident once they're pointed out. For instance, if yo But there are times when a simple laundry list of contributing locations isn't enough to understand an issue. For instance, when a null pointer can be dereferenced on some paths through the code, what you really need are issue flows. Each flow is a _set_ of secondary locations ordered to show the exact path through the code on which a problem can happen. And because there can be multiple paths through the code on which, for instance a resource is not released, {instance} supports multiple flows. +Check out this [ video](https://youtu.be/17G-aZcuMKw) for more on issues with multiple locations. + ## Issues lifecycle ### Statuses After creation, issues flow through a lifecycle, taking one of five possible statuses: |