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

Admin UI source dropdowns inappropriately advance

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Blocker
    • Resolution: Fixed and reviewed
    • Affects versions: 2.2.0, 2.3.0
    • Fix versions: 2.3.0
    • Labels:
      None
    • Severity:
      Incorrectly Functioning With Workaround
    • Steps to reproduce:
      Hide
      Steps to reproduce:
      1. Start scheduling a capture, and finish off the Source page but do not click Next
      2. Reselect one of the dropdown fields (ie, if the duration hour value was 01, select it again)
       
       Actual Results:
       Your field's value advances by one (1 hour becomes 2, etc). This is *not* reflected in the UI, which still shows the correct, but the scheduled values are incorrect - as shown in the Summary screen. Setting the field to the same value again does nothing - it does not retrigger the event validation code as it previously did. Setting the field to another value works as expected, and will allow you to set it back to the original value correctly as well.
       
       Expected Results:
       The field should be set to the correct value.
       
       Workaround (if any):
       If this behaviour is triggered it can be cleared by refreshing the page, or setting the field to an alternate value before setting it to the correct value. For example, change the duration to 3 hours, then back to 1 hour.





      Show
      Steps to reproduce: 1. Start scheduling a capture, and finish off the Source page but do not click Next 2. Reselect one of the dropdown fields (ie, if the duration hour value was 01, select it again)    Actual Results:  Your field's value advances by one (1 hour becomes 2, etc). This is *not* reflected in the UI, which still shows the correct, but the scheduled values are incorrect - as shown in the Summary screen. Setting the field to the same value again does nothing - it does not retrigger the event validation code as it previously did. Setting the field to another value works as expected, and will allow you to set it back to the original value correctly as well.    Expected Results:  The field should be set to the correct value.    Workaround (if any):  If this behaviour is triggered it can be cleared by refreshing the page, or setting the field to an alternate value before setting it to the correct value. For example, change the duration to 3 hours, then back to 1 hour.

      TestRail: Results

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              greg_logan Greg Logan
            • Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                TestRail: Cases