Uploaded image for project: 'Opsgenie'
  1. Opsgenie
  2. OPSGENIE-1925

Ablity have a unique ID for historical and default types in schedule timeline API endpoint

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • Teams - API
    • None
    • 0

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      User Problem

      Currently, in response to the payload sent by the schedule timeline API endpoint, We send two objects, historical and default when the rotation starts and ends between two different dates. The end time in historical has the today's date and the end time in default has the actual date.

      Suggested Solutions

      Give a unique ID for the same rotation that starts and ends between two dates or give them as one entry in the response payload.

      Current Workarounds

      Currently, you need to match the user ID and type to find the start and end date.

              Unassigned Unassigned
              e36795e75cab Tejaswi G (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: