Customizable time/closing thresholds for Jira automated checks

Problem:
Currently, the time thresholds for Jira automated checks are fixed and cannot be customized to match users’ internal policies and workflows. This leads to checks failing even when the underlying processes are being followed correctly.

Requested Improvement:
Allow users to customize SLA/Closing thresholds for Jira automated checks based on their internal policies.

Ideally, users should also be able to configure which date triggers the SLA calculation (e.g., ticket creation date vs. employee departure/due date).