Uploaded image for project: 'PUBLIC - Liferay Portal Community Edition'
  1. PUBLIC - Liferay Portal Community Edition
  2. LPS-89119

[SLA] Define working hours that should be counted against SLAs

    Details

    • Branch Version/s:
      7.2.x
    • Backported to Branch:
      Committed
    • Epic Link:
    • Sprint:
      Workflow_7.2_12, Workflow_7.2_13

      Description

      As a process owner, I want to define the SLA timer calendar, so I can track items according to my business working hours.

      Context: workflow metrics application can be extended to support custom calendars that can be used when defining process SLAs. To do so, customers will have to implement it by their own.

      Acceptance Criteria

      • At the SLA form, the Duration Time section should have the title updated to Duration;
      • The section description should have different messages depending on the following situations:
        • If no custom calendar exist, the message is: Define the SLA duration. By default, the SLA timer runs 24 hours per day, 7 days per week.
        • If custom calendar exist, the message is: Define the SLA duration and timer format.
      • The section should have different fields depending on the following situations:
        • If no custom calendar exist, the field "Calendar" won't be displayed at the page;
        • If custom calendars exist, the field "Calendar" should be displayed at the page;
      • Customers will have total responsibility for the custom calendars name, schedule and time-zone, wether they will consider specific time zones, weekdays and/or holidays;
        • The SLA form will display only the calendars name at the Calendar select field;
      • If custom calendars exist, they should be available for all processes to consume;
        • The 24/7 schedule will be selected by default. This should always be the first option at the dropdown list;

      Definitions of Done

      • Related tests created and passed successfully;
      • All Acceptance Criteria were passed;
      • Make sure that all system documentation were updated (if necessary);
      • Validated by QA, Product Designer and/or PM;
      • No critical issue related to Story scope (ex.: similar of a FP4, FP5 bug);
      • Code with peer review completed.

      Design Deliverables

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              support-qa Support QA
              Reporter:
              nathalia.moura Nathália Moura (Inactive)
              Recent user:
              Rodrigo Cunha
              Participants of an Issue:
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Packages

                  Version Package
                  7.2.X
                  Master