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

[Performance] View the evolution/involution of my process velocity through time

    Details

      Description

      As an operation manager, I want to see the evolution/involution of my process velocity results through time, so that I can compare the results in different periods. 

      Context

      Velocity/Throughput Metrics over time
      Once the velocity/throughput is a very good parameter to measure the performance of a workflow, we need to provide a way to let the user understand the evolution or involution of each of his processes' velocity. To achieve that, we chose to represent this metric as a line chart with a configurable time frame and unit of the velocity, allowing him to adapt the chart to his attend his needs and easily understand the performance through time.

      Acceptance Criteria

      • Given a process with several completed instances along a timeframe, when the user decides to analyze this process velocity metrics, then he should be able to understand if his velocity has improved or declined along the timeframe;
      • Given a process with several completed instances along a timeframe, when the user is analyzing the velocity of this process, then he should be able to identify what was the velocity of the process in specific points along the timeframe;
      • If there is an unexpected error, the card should display the specific error state (as specified on Figma);
      • At the chart, the velocity unit choice will inform the granularity of the data that is displayed on the x-axis (meaning the number and unit of data points);
        • Depending on the selected time range option, the velocity unit options will update accordingly.
        • For each time range option, there will be a default velocity unit option, and users can select other options if available, as described bellow.

      Time period rules => Full documentation at this link;

      • Yesterday: from 00:00 to 23:59 of the previous day, displayed in hours, 24 points, 5 labels (12AM, 6AM, 12PM, 6PM 11:59PM);
      • Today: from 00:00 to the next nearest hour of the current day, displayed in hours, 2 to 24 points, 2 to 5 labels (in hours, eg.: 12 AM);
      • Last 7 days: from 6 days ago to today, displayed in days, 7 points, 7 labels (in days, eg.: 26 Jun or 2 Jun);
      • Last 30 days: from 29 days ago to today,
        • (Default) Displayed in days, 30 points, 6 labels (in days);
        • Displayed in weeks, starts on Sunday, 4 or 5 points (the first/last week can have less than 7 days), 4 or 5 labels (day ranges per week, eg.: 9-15 Jun or 28 Jun - 3 Aug);
      • Last 90 days: from 89 days to today,
        • Displayed in days, 90 points, 3 or 4 labels (in months);
        • (Default) Displayed in weeks, starts on Sunday, 13 or 14 points (the first/last week can have less than 7 days), 7 or 8 labels (day ranges per week);
        • Displayed in months, 3 or 4 points (the first/last month can have less than 30 days), 3 or 4 labels (in months);
      • Last 180 days: from 179 days ago to today
        • Displayed in weeks, starts on Sunday, 25 or 26 points (the first/last month can have less than 30 days), 6 or 7 labels (in months);
        • (Default) Displayed in months, 6 or 7 points (the first/last month can have less than 30 days), 6 or 7 labels (in months);
      • Last Year: from 364 or 365 days to today,
        • Displayed in weeks, starts on Sunday, 51 or 52 points (the first/last week can have less than 7 days), 7 or 8 labels in months;
        • (Default) Displayed in months, 12 or 13 points (the first/last month can have less than 30 days), 6 or 7 labels;

      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

      Features that doesn't need to be implemented yet:

      • The "All time" option of the time frame choice (this option was dropped and will be addressed in LPS-98233)

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              matheus.xavier Matheus Xavier
              Reporter:
              nathalia.moura Nathália Moura (Inactive)
              Engineering Assignee:
              Nathália Moura (Inactive)
              Recent user:
              Rodrigo Cunha
              Participants of an Issue:
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Packages

                  Version Package
                  Master