Uploaded image for project: 'OpenShift GitOps'
  1. OpenShift GitOps
  2. GITOPS-5572

Timestamp for Application Health Status

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Unresolved
    • Icon: Normal Normal
    • None
    • None
    • ArgoCD
    • None
    • 5
    • GitOps Crimson - Sprint 3263
    • Customer Facing, Customer Reported

      Story (Required)

      Currently there is no way to know when the Application health status was changed or how long it is in the same state. Having timestamps in Application health status would help. Few use cases are mentioned in https://github.com/argoproj/argo-cd/issues/16972 .

      Background (Required)

      This feature is required to fix a bug in notification triggers. GITOPS-3699

      Approach (Required)

      Acceptance Criteria (Mandatory)

      • PR is merged in upstream

         

        INVEST Checklist

      Dependencies identified

      Blockers noted and expected delivery timelines set

      Design is implementable

      Acceptance criteria agreed upon

      Story estimated

      Legend

      Unknown

      Verified

      Unsatisfied

      Done Checklist

      • Code is completed, reviewed, documented and checked in
      • Unit and integration test automation have been delivered and running cleanly in continuous integration/staging/canary environment
      • Continuous Delivery pipeline(s) is able to proceed with new code included
      • Customer facing documentation, API docs etc. are produced/updated, reviewed and published
      • Acceptance criteria are met

              rh-ee-sghadi Siddhesh Ghadi
              rh-ee-sghadi Siddhesh Ghadi
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: