Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat(SLA): Apply SLA to any document #22449

Merged
merged 74 commits into from
Jun 14, 2021
Merged

Conversation

hrwX
Copy link
Contributor

@hrwX hrwX commented Jun 25, 2020

This PR enables setting Service Level Agreement for any doctype.

Document Type field added to SLA doctype

document_type

SLA fields

On creating the SLA, an SLA section will get added to the selected doctype with the following fields (custom fields for standard doctype and docfields for custom doctype).

  • Service Level Agreement
  • Priority
  • Response By
  • Response By Variance
  • Resolution By
  • Resolution By Variance
  • First Responded On
  • On Hold Since
  • Total Hold Time
  • Agreement Status
  • SLA creation
  • Resolution Date

custom_dt_with_sla

Hold Time

Hold Time is captured if the Pause SLA On configuration is setup in SLA

sla-hold-time.mp4

SLA Fulfilled On

Allows you to configure statuses for SLA fulfillment

image

Apply SLA for Resolution Time

For a few instances like applying SLA on leads, there is no resolution SLA required. The only metric that matters is the First Response Time. Hence, the SLA application for resolution time is now optional. If it is disabled, the SLA status is validated as Fulfilled / Failed on the basis of first response time only.

image

sla-on-response-only.mp4

Hooks

  1. Applying SLA
  2. Setting hold time on communication update
  3. Setting SLA variance

Documentation PR: frappe/erpnext_documentation#340

@hrwX hrwX requested a review from marination as a code owner June 25, 2020 10:07
@rohitwaghchaure rohitwaghchaure added the CI-failing Unit tests or patch tests are failing. label Jun 28, 2020
@ruchamahabal ruchamahabal removed the needs-tests This PR needs automated unit-tests. label May 29, 2021
@barredterra
Copy link
Collaborator

@hrwX do you remember why you decided to convert timestamps to the user timezone in the backend for this feature? It seems like all other code works with the system timezone in the backend and lets the UI/frontend convert to/from the user timezone.

We're currently contemplating to remove this.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 20, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants