Prepare docs for release 26.0.3

Author: Yuliya_Prihodko

docs/dashboards-and-widgets/CumulativeTrendChart.mdx

@@ -22,6 +22,7 @@ A widget does not require an edit or new filter creation. If a new version (buil
 <MediaViewer src={require('./img/widget-types/CumulativeCreation.png')} alt="Cumulative Creation" />
 
 **Widget view**
+
 A widget has two levels.
 
 **For the first level**  the system uses the last 600 launches from the chosen filter.
@@ -47,35 +48,39 @@ Statistics for bars BUILD: 3.20.8.0 is calculated as - a summary of latest launc
 
 <MediaViewer src={require('./img/widget-types/CumulativeTrendChart.png')} alt="Dashboard to manage test results: Cumulative trend chart First Level View" />
 
-A user can drill down to the second level of the widget. For that, he should click on the bar. And the system shows two buttons: Drill Down and Show filter.
-And a user should click on **"Drill down"**.
+Users can drill down to the second level of the widget by clicking a bar in the chart. The system displays the **Drill down** and **Show Filter** options. To open the second-level view, the user should select **Show Filter**.
+
+The system opens a filtered list of tests corresponding to the selected segment.
+
+* Clicking **Passed** displays only Passed tests.
+* Clicking **Failed** displays Failed and Interrupted tests.
+* Clicking **Skipped** displays only Skipped tests.
+* Clicking a defect type displays tests with the corresponding defect type.
 
 **For the second level** the system again analyzes the 600 launches from the filter.
 Then it leaves only launches that have an attribute, that has been clicked by the user (f.e. BUILD: 3.20.8.0 ).
 From these launches, systems choose ones with attributes that have key attribute from the section Level 2 (detailed view) on widget wizard.
 After the system groups launch with the same attribute and leaves for each selection only the “latest” launches (launches with unique launch name and with the biggest launch number in ReportPortal).
 Others should be removed from a group. Each unique group should be reflected in the graph on the second widget level.
 
-
-For each group there is shown a set of bars: Passed, Failed, Skipped, group Product Bug, group Auto Bug, group System Issue, group No defect, group To investigated.
+Status and defect statistics bars are displayed for each group. The status statistics bar includes Passed, Failed, and Skipped statuses. The defect statistics bar includes the following groups: Product Bug, Automation Bug, System Issue, No Defect, and To Investigate.
 
 On the hover on the bar, a user can see detailed information about the sample. Also, the user can see a list of attributes with attribute key from the first and from the second level which has launches, which have been used for a hovered bar.
 
-
 **Visual options**
 
-**Focus on defect types**
+**Defect types**<br />
 If the option is enabled, a user can see only information about defect types for each sample.
 If an option is disabled, a user can see information about statuses and defect types.
 
-**Totals**
+**Totals**<br />
 If the option is enabled, a user can see info about several test cases in each sample.
 
-**Staked area / Separate bars**
+**Staked area / Separate bars**<br />
 Staked area chart - is shown one bar for statuses, and one bar for defect types for each sample.
 Separate bars - is shown a separate bar for each status, and each defect type group.
 
-**Tests / Per cent**
+**Tests / Percent test mode**<br />
 Test mode - OY axis is calculated in test cases.
 Percent mode - OY axis is calculated in percent. OY = 100%.
 

docs/dashboards-and-widgets/FlakyTestCasesTableTop50.mdx

@@ -47,4 +47,8 @@ The number of switches from one state to another of the test case with the same
 On mouse hover, tooltip appears “N status changes from M possible times”.
 :::
 
+**Drill-down behavior**
+
+When a user clicks a test case in the Flaky Test Cases widget, ReportPortal redirects the user to the most recent available execution of the selected test case and displays its execution details.
+
 <MediaViewer src={require('./img/widget-types/FlakyTestCasesTableWidget.png')} alt="Data visualization in test automation: Flaky Test Cases Table Widget" />

docs/dashboards-and-widgets/OverallStatistics.mdx

@@ -15,13 +15,23 @@ The panel shows a summary of test cases with each status for each selected launc
 - Widget Criteria: All criteria are selected by default.
 - Type of view: Panel view/ Donut view
 - Mode All launches/ Latest launches
+- 'Show the "Interrupted" status independently from "Failed" items' checkbox (unselected by default)
 
 
 **Widget view**
 
 The widget shows statistics of the All launches/or Latest launches for the chosen filter. Statistics are divided into the following sections:
--    Skipped, Passed, Failed
--    Product Bug, System Issue, Automation Bug, No Defect and To Investigate.
+-  Skipped, Passed, Failed, Interrupted (*)
+-  Product Bug, System Issue, Automation Bug, No Defect and To Investigate.
+
+\* The widget view depends on the state of the 'Show the "Interrupted" status independently from "Failed" items' checkbox:
+
+- If the **checkbox is unselected**, Interrupted tests are included in the Failed count.
+- If the **checkbox is selected**, failed tests are divided into Failed and Interrupted categories independently, regardless of the selected view type (Panel view or Donut view).
+
+<MediaViewer src={require('./img/widget-types/OverallStatisticsInterrupted1.png')} alt="Show the Interrupted status checkbox" />
+
+<MediaViewer src={require('./img/widget-types/OverallStatisticsInterrupted2.png')} alt="Included Interrupted tests" />
 
 The statistics for every type are shown in percentages. On hover, the exact number is shown for each type.
 The Widget has clickable sections when you click on a specified section in the widget, the system forwards you to launch view for appropriate selection.

docs/dashboards-and-widgets/TestCaseSearch.mdx

@@ -17,7 +17,7 @@ Allows finding a test case by name or attribute throughout all launch executions
 
 ### Refine section:
 
-- "Test name" text field. Condition dropdown is disabled. By default – cnt (contains)
+- "Test name" text field. Condition dropdown is disabled. By default – starts with
 - "Attribute" text field – key and value options
 - "Display launches" toggle – default state: OFF
 - "Edit" icon
@@ -84,40 +84,34 @@ If more than one page exists for the specified search criteria, a "Load more" bu
 
 <MediaViewer src={require('./img/widget-types/TestCaseSearch7.png')} alt="Load more button" />
 
-By clicking "Load more", additional 10 results (or less if available) appear. Previously loaded results remain visible and are supplemented with new data. If at least one more page is available, the "Load more" button continues to appear at the bottom of the widget.
+By clicking “Load more,” up to 10 additional results appear, depending on how many results are available. Previously loaded results remain visible and are supplemented with new data. The maximum number of search results is 20 items.
 
-If more than 30 pages exist for the specified search criteria, the "Load more" button becomes disabled after loading the 30th page. The limit for the widget is 300 latest test cases.
-
-<MediaViewer src={require('./img/widget-types/TestCaseSearch8.png')} alt="Load more button becomes disabled" />
+If you need more flexible search options, advanced filtering, sorting, or access to a larger result set, try our premium feature: [Test Executions](/features/TestExecutions/). Learn which [plan](https://reportportal.io/pricing/saas/) best fits your testing needs.
 
 When the "Display launches" toggle is ON, the displayed results are grouped by launch execution and parent items (Launch/suite/test).
 
-<MediaViewer src={require('./img/widget-types/TestCaseSearch9.png')} alt="Display launches toggle is ON" />
+<MediaViewer src={require('./img/widget-types/TestCaseSearch8.png')} alt="Display launches toggle is ON" />
 
 By clicking on the "Update" icon the page is refreshed a new request with specified in the widget parameters is sent. Only the first page is displayed.
 
-<MediaViewer src={require('./img/widget-types/TestCaseSearch10.png')} alt="Update icon" />
+<MediaViewer src={require('./img/widget-types/TestCaseSearch9.png')} alt="Update icon" />
 
 By clicking on the test name, the user is redirected to the test's log level in a new tab (the same action occurs when clicking the icon next to the test name).
 
-<MediaViewer src={require('./img/widget-types/TestCaseSearch11.png')} alt="Test's log level" />
+<MediaViewer src={require('./img/widget-types/TestCaseSearch10.png')} alt="Test's log level" />
 
 If a test item has a long description, an arrow appears to expand it.
 
-<MediaViewer src={require('./img/widget-types/TestCaseSearch12.png')} alt="An arrow to expand description" />
-
-<MediaViewer src={require('./img/widget-types/TestCaseSearch13.png')} alt="A long description" />
+<MediaViewer src={require('./img/widget-types/TestCaseSearch11.png')} alt="An arrow to expand description" />
 
 When hovering over the Start Time field, the format changes while hovering; clicking changes it per application settings.
 
-<MediaViewer src={require('./img/widget-types/TestCaseSearch14.png')} alt="Start Time field" />
+<MediaViewer src={require('./img/widget-types/TestCaseSearch12.png')} alt="Start Time field" />
 
 Sorting is available by the Start Time field, with descending order set by default. Users can switch between ascending and descending order.
 
 By clicking the link to the bug tracking system, the ticket in the BTS opens.
 
-<MediaViewer src={require('./img/widget-types/TestCaseSearch15.png')} alt="The link to the bug tracking system" />
-
-<MediaViewer src={require('./img/widget-types/TestCaseSearch16.png')} alt="The ticket in the bug tracking system" />
+<MediaViewer src={require('./img/widget-types/TestCaseSearch13.png')} alt="The link to the bug tracking system" />
 
 <MediaViewer src="https://youtu.be/HxHCJTNqGaY" alt="Test Case Widget" type="video" />