Right now problem notification filtering is on impact level (Application, Service, Infrastructure). This will be replaced with severity level filtering within the next 4 weeks. The new severity levels will be AVAILABILITY, ERROR, SLOWDOWN, RESSOURCE_CONTENTION and CUSTOM. See a screenshot of the new powerful notification filtering feature that is upcoming:
The severity elevation logic is that AVAILABILITY comes first, followed by ERROR, SLOWDOWN and RESOURCE_CONTENTION. So a problem that starts as a SLOWDOWN will immediately raised to highest AVAILABILITY level once the Dynatrace AI detects any hint for an outage or host or process unavailability.
How we can map the priorities in Dynatrace (AVAILABILITY, ERROR, SLOWDOWN, RESOURCE_CONTENTION and CUSTOM) to the priorities in Jira (Blocker, Critical, Major, Minor and Trivial) ??