Skip to content

Commit 84095ab

Browse files
aluca3gitbook-bot
authored andcommitted
GITBOOK-8473: vc-CB docs: remove jira policy and actio
1 parent 49e2982 commit 84095ab

File tree

4 files changed

+0
-135
lines changed

4 files changed

+0
-135
lines changed

docs/SUMMARY.md

-1
Original file line numberDiff line numberDiff line change
@@ -773,7 +773,6 @@
773773
* [Classification policy - Use case](manage-risk/policies/assets-policies/use-cases-for-policies/classification-policy-use-case.md)
774774
* [Tagging policy - Use case](manage-risk/policies/assets-policies/use-cases-for-policies/tagging-policy-use-case.md)
775775
* [Notification policy - Use case](manage-risk/policies/assets-policies/use-cases-for-policies/notification-policy-use-case.md)
776-
* [Jira policy - Use case](manage-risk/policies/assets-policies/use-cases-for-policies/jira-policy-use-case.md)
777776
* [Use policies in the SDLC](manage-risk/policies/use-policies-in-the-sdlc.md)
778777
* [Security policies](manage-risk/policies/security-policies/README.md)
779778
* [Create a security policy and rules](manage-risk/policies/security-policies/create-a-security-policy-and-rules.md)

docs/manage-risk/policies/assets-policies/create-policies.md

-1
Original file line numberDiff line numberDiff line change
@@ -105,7 +105,6 @@ After defining filter components, you need to define the actions that the policy
105105
* **Set Asset Class** - Sets the class on the matched assets. Removing the policy or turning in off does not retroactively change the asset class back to default.
106106
* **Set Asset Tag** - Sets a tag on the matched assets. Removing the policy or turning in off will remove the tags of this policy from the relevant assets.
107107
* **Set Coverage Control Policy** - Sets a control on filtered assets that checks whether selected security products are scanning assets, optionally within a given timeframe. Assets that fail this control will be marked accordingly on inventory pages. This control applies the OR logic across products.
108-
* **Set Jira policy -** Automate the creation and management of Jira tickets based on specific conditions related to your assets. You can create new Jira tickets for new matches that meet the policy criteria, modify existing Jira tickets if the policy conditions change, set classifications and tags on assets using the policy, or notify users using Slack or email when a condition is met.
109108

110109
<figure><img src="../../../.gitbook/assets/Policy - Nwe UI.png" alt="AppRisk - Set a policy action"><figcaption><p>Snyk AppRisk - Set a policy action </p></figcaption></figure>
111110

docs/manage-risk/policies/assets-policies/use-cases-for-policies/README.md

-1
Original file line numberDiff line numberDiff line change
@@ -7,6 +7,5 @@ Gain a better understanding of the policies you can use by going through the fol
77
* [Classification](classification-policy-use-case.md)
88
* [Tagging](tagging-policy-use-case.md)
99
* [Notifications](notification-policy-use-case.md)
10-
* [Jira ticket creation](jira-policy-use-case.md)
1110

1211
Each type of policy is accompanied by a use case, explaining a practical way of using the policy. The use cases provide a clear example of one of the possible ways of using the policy and offer details about the conditions needed for the filters and actions when building your policy.

docs/manage-risk/policies/assets-policies/use-cases-for-policies/jira-policy-use-case.md

-132
This file was deleted.

0 commit comments

Comments
 (0)