Uploaded image for project: 'CloverDX'
  1. CloverDX
  2. CLO-10134

Last execution and successes/failures count in listeners table

    XMLWordPrintable

Details

    • Story
    • Status: Closed
    • Major
    • Resolution: Fixed
    • None
    • rel-4-6-0-M1
    • Server
    • Security Level: Users (General product issues)
    • 5
    • UNDECIDED
    • BRQ Sprint 32, BRQ Sprint 33, BRQ Sprint 34, BRQ Sprint 35

    Description

      When I need to see current state of automatic processing, I want to see overview of my listeners. I need to be able to see:

      • do listeners run
      • is listener failing (and how many times during last 24 hours)
      • is listener triggering its task (and how many times during last 24 hours)

      For failed or successful runs, I want to be able to go directly into Task History from here.

      Add "Last run", "Successful triggers count" and "Failures" columns into listeners table.

      See attached wireframe (ignore checks column, Successful triggers count will be there instead). Interval selection is part of another story.

      Failure means both check failure or related task failure.

      Success means success triggered task (= it is not failure and it is not check only).

      Acceptance criteria

      • There is timestamp showing last activity of listener in table
      • There are columns showing count of successful/failed triggered actions in table
      • It is possible to click on values in count columns and it will lead into Task History with proper filter set
      • Links are underlined on mouse over
      • Failures means both check failure and task failure

      Attachments

        Issue Links

          Activity

            People

              sedlacekj Jan Sedlacek (Inactive)
              sedlacekj Jan Sedlacek (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0 minutes
                  0m
                  Logged:
                  Time Spent - 4 days
                  4d