Automation | All automations did not display in the list, when running a search in the Automations library and clearing the search field, |
General | Pressing the tab key closed the edit modal without saving the changes, when editing a Markdown field in an incident layout, Adding a number and then deleting that number in the column resulted in an error, when editing a grid field that included a number column. The date field's calendar modal was cut off at the bottom, preventing confirmation of the selected date, when using a low resolution and viewing a layout, When pasting text into the middle of a note and the markdown toolbar was present, the text would be pasted in the right place, but the cursor would jump to the end of the note. There was no scrolling enabled in dialog boxes, which occasionally caused the dialog box's buttons to be cut off the screen.
|
Incidents | Part of the data was cut off and did not appear in the CSV file, when exporting data to CSV format from a table in a dynamic section of an incident layout. The markdown field did not display in incident layouts, when a markdown field contained an indicator. There was no option for removing a filter, when creating a pre-process rule. The section search field overlapped with the section header, when adding a new dynamic section to an incident layout, If you viewed a sub-playbook from the Work Plan and then navigated to another incident , when you returned to the same Work Plan in the previous incident, the sub-playbook appeared, rather than the main playbook. In the incident layout builder, the dialog box was small and difficult to use , when adding a field with a conditional filter, A custom incident field from another incident was added to an incident even though its incident type did not include the custom incident field.
|
Indicators | In some cases, not all indicators marked for expiration expired. Any change in the indicator's field changed the type to type IP, when adding or editing a URL indicator with an IP address in it (http://<ipaddress>/endpoint), To prevent the number of related incidents of an indicator that are stored in the indicator from increasing significantly causing memory issues/outage on the server, a new configuration key named indicator.investigationids.maxlen was created. When defined, the number of associated investigation IDs saved per indicator will be limited to "maxlen". If a new ID is associated with the indicator, the oldest ID will be removed. Use 0 for "unlimited" (the default and current behavior).
|
Jobs | After creating a job with a specific form, when opening the edit form page, it contained the fields from a different job form. IYou could not access the Jobs page, when changing the cron job to an invalid value.
|
Lists | Tabs were saved as spaces in the Lists editor. |
Multi-tenant | (Multi-tenant) The dynamic section was empty when viewed from the Main account, but displayed correctly on the tenant account, when viewing an incident with a dynamic section in the incident layout. |
Playbooks | When adding tasks to a playbook, they were placed in random, hard to find locations. Files created by an automation or playbook with quiet mode were not useable and could not be referenced. When editing the reply options in a data collection task with First option is default selected, editing a reply option overwrote the option above it. Error tasks did not show as errors (highlighted in red) if the task was configured to continue on error.
|
Reports | When a report was exported to PDF format, detailed information about timer fields was missing from the report. |
System diagnostics | In some cases, the Delete audits button on the System Diagnostics page did not work correctly. The button has been removed and replaced with a link to instructions for deleting audit logs. |
War Room | The scroll buttons did not work, when entries were loading in the War Room, The upper scroll did not work, when there were more than 200 entries in the War Room and a filter was added and then removed.
|