You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/content/asset_modelling/engagements_tests/OS__engagements.md
+7-9Lines changed: 7 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -56,11 +56,11 @@ As the containers that organize testing activity, Engagements can store or track
56
56
57
57
Engagements are accessible via the sidebar. The submenu provides access to Active Engagements and All Engagements, as well as the option to view Engagements as organized by Product, Test types, and Environments.
58
58
59
-
59
+
60
60
61
61
Alternatively, Engagements within a particular Product can be accessed from the submenu of the Engagements option in the top bar.
62
62
63
-
63
+
64
64
65
65
### Permissions
66
66
@@ -74,7 +74,7 @@ There are multiple approaches to creating an Engagement. Each approach requires
74
74
75
75
Once you’ve created a Product, you can add a new Interactive or CI/CD Engagement in the Engagements section of the Product’s navigation bar.
76
76
77
-
77
+
78
78
79
79
Every Engagement must have the following fields defined:
80
80
- Type (Interactive or CI/CD)
@@ -108,25 +108,23 @@ Engagements can be edited by clicking the **Edit** button within the Engagement
108
108
109
109
You can easily duplicate Engagements by navigating to the list of Engagements within a Product and clicking the **Copy** button from within the ⋮ kebab menu next to the Engagement to be copied. This will create an exact copy of the original Engagement within the parent Product, including the metadata, Tests, and Findings within it.
110
110
111
-
111
+
112
112
113
113
### Close Engagements
114
114
115
115
Engagements can be closed by navigating to the list of Engagements within a Product and clicking “Close” from within the ⋮ kebab menu of the chosen Engagement.
116
116
117
-
117
+
118
118
119
119
Once closed, the Engagement’s status will be changed to “Completed.” Nevertheless, most write operations (e.g., adding tests, importing scans) will remain available.
120
120
121
121
Closing an Engagement does not change the status of the Findings within any of the Engagement’s Tests. Findings remain open, mitigated, or risk accepted according to their own lifecycle, and remain accessible for viewing and reporting.
122
122
123
-
@paulOsinski Add additional details about Jira here — If the Engagement is linked to a Jira Epic, closing the Engagement will trigger an asynchronous task that closes the associated Jira Epic.
124
-
125
123
### Reopen Engagements
126
124
127
125
If an Engagement is closed, it can be reopened by clicking **Reopen** from within its ⋮ kebab menu in the Closed Engagements table. This will make the Engagement active again and return its status to “In Progress.”
128
126
129
-
127
+
130
128
131
129
### Expired Engagements
132
130
@@ -138,7 +136,7 @@ Once expired, a red “X days overdue” notification will appear in the Engagem
138
136
139
137
While it is not enabled by default, there is an option within the system settings to auto-close an Engagement once it has been expired for a certain number of days.
Copy file name to clipboardExpand all lines: docs/content/asset_modelling/engagements_tests/PRO__engagements.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -56,11 +56,11 @@ As the containers that organize testing activity, Engagements can store or track
56
56
57
57
Engagements are accessible via the sidebar. The submenu provides access to Active Engagements and All Engagements, as well as the option to create new Engagements.
58
58
59
-
59
+
60
60
61
61
Alternatively, Engagements within an Asset can be accessed in the window at the bottom of the Asset’s view.
62
62
63
-
63
+
64
64
65
65
### Permissions
66
66
@@ -77,19 +77,19 @@ There are several ways to create an Engagement:
77
77
- Within the Engagements dropdown in the Manage section of the sidebar
78
78
- You will have to select the Asset to which to attribute the Engagement when completing the New Engagement form
79
79
80
-
80
+
81
81
82
82
- The gear icon located at the top right corner of an Asset view
83
83
84
-
84
+
85
85
86
86
- The “+ New Engagement” button found in the list of Engagements within an Asset
87
87
88
-
88
+
89
89
90
90
- If you haven’t already created an Engagement within an Asset, you can do so while importing a scan.
91
91
92
-
92
+
93
93
94
94
Every Engagement must have the following fields defined:
0 commit comments