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

[Reports] View the summary of pending items that doesn't have SLAs applied to them

    Details

    • Branch Version/s:
      7.2.x
    • Backported to Branch:
      Committed
    • Sprint:
      Workflow_7.2_10, Workflow_7.2_11

      Description

      As a process owner, I want to view the summary of pending items that doesn't have SLAs applied to them.

      Acceptance Criteria

      • The Pending Items card will classify items as Overdue, On Time and Untracked;
        • The metrics for Due In 7 Days and Due After 7 days should be replaced by On Time;
        • Consider as Untracked the total number of pending instances that didn't trigger any SLA targets yet;
        • Consider as On Time the total number of pending instances that triggered at least one SLA AND didn't breach any SLA targets;
        • Consider as Overdue the total number of pending instances that breached one or more SLAs target times;
      • The sum for items Overdue + On Time + Untracked should be equal to the Total Pending;
      • The card title top margin should be according to the mockup;
      • The info icon hover state and tooltip size should be according to the mockup;
      • The tooltip message should be updated according to the mockup "Pending workflow items are counted and categorized by their SLA status.";
      • If a user update the Report page that has an empty card and after that a new data arise the card state must change from empty to populated;
      • If there is an unexpected error, the card should display the specific error state (as specified at the Components page on Figma);
      • If there is no SLA defined for the process, the the metrics for Overdue and On Time should be zero "0";
      • For numbers greater than 4 digits, use abbreviation standards considering localization specifications (example for english: replace 10,220 for 10.2K);

      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 an FP5 bug);
      • Code with peer review completed.

      Design Deliverable (Review Workflow and Component page on Figma):

        Attachments

          Issue Links

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Packages

                  Version Package
                  7.2.X
                  Master