Uploaded image for project: 'Opencast'
  1. MH-11703

Service error states not immediately visible in admin UI

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed and reviewed
    • Affects Version/s: 2.2.0, 3.2
    • Fix Version/s: 4.0
    • Labels:
      None
    • Severity:
      Usability Issue
    • Steps to reproduce:
      Hide
      Steps to reproduce:

      1. Create an error state in a service (e.g. incorrect config)
      2. Notice that some jobs are not running
      3. Go to System / Services
       
       Actual Results:
       
       The default sort order means that a long list of NORMAL services is shown, and you have to explicitly sort by Status to see that one is in ERROR.

       Expected Results:
       
      1. There should be a global visual indicator in the UI that one or more services is in ERROR state (e.g. exclamation mark or alert message)

      2. When you go to the Services page, the default sort order should be to show services in ERROR.
       
       Workaround (if any):
       
      Be vigilant, and sort by Status.
      Show
      Steps to reproduce: 1. Create an error state in a service (e.g. incorrect config) 2. Notice that some jobs are not running 3. Go to System / Services    Actual Results:    The default sort order means that a long list of NORMAL services is shown, and you have to explicitly sort by Status to see that one is in ERROR.  Expected Results:   1. There should be a global visual indicator in the UI that one or more services is in ERROR state (e.g. exclamation mark or alert message) 2. When you go to the Services page, the default sort order should be to show services in ERROR.    Workaround (if any):   Be vigilant, and sort by Status.

      TestRail: Results

        Attachments

          Issue links

            Activity

              People

              • Assignee:
                greg_logan Greg Logan
                Reporter:
                smarquard Stephen Marquard
              • Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  TestRail: Cases