Add a Rotation multi‑select filter to the "Total time per user (removing overlaps)" Opsgenie on‑call report, so that total on‑call time per user can be calculated only for selected rotations, instead of always aggregating across all rotations.

XMLWordPrintable

    • 1

      Problem

      • In JSM Operations, a single user can belong to multiple on‑call rotations (e.g. A, B, C, D).
      • In many real scenarios, only some of those rotations are billable/paid (e.g. A and D), while others (B and C) are not.
      • The current "Total time per user (removing overlaps)" report always aggregates across all rotations the user is part of.
      • There is no way to restrict that top summary table to specific rotations. As a result:
        • The total time per user includes non‑payable rotations, and
        • Teams cannot directly use this report for accurate payment / compensation calculations.

      The "On call segmentation - Global" section does list data per rotation and includes a Rotation column, but it does not provide a simple, aggregated per‑user total for selected rotations, equivalent to the first table.

      Suggested Solution

      • In the JSM operations report UI, enhance the "Total time per user (removing overlaps)" view with a Rotation filter that:
        • Allows multiple selection (multi‑choice) of rotations.
        • Is optional / not mandatory - if left empty, the behaviour remains "all rotations" (current default).
        • When specific rotations are selected (e.g. A and D), the per‑user totals in the first table are calculated only from those rotations, excluding time from all others (e.g. B and C).

      Why This Is Important

      • Accurate payment / billing: Many customers only pay for time spent in specific rotations. Without a rotation filter, the main per‑user report overstates payable time, as it includes non‑billable rotations.

      Workaround

      (Add a workaround, if available)

            Assignee:
            Unassigned
            Reporter:
            Shakti
            Votes:
            1 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: