Maintenance update incorrectly state no component is affected if component already in maintenance state

XMLWordPrintable

    • 1
    • Severity 3 - Minor

      Issue Summary

      When using Maintenance automation to update component status, if the component is already in maintenance, the update will show "No components were marked as affected by this incident."

      Steps to Reproduce

      1. Modify the component state to "Under Maintenance" on the component screen.
      2. Schedule Maintenance with the same component marked to be affected.
      3. Make sure in the automation section, options under: "At the start time for this maintenance" are both ticked:
        • Set status to 'In Progress'
        • Set affected components' status to 'Under Maintenance'
      1. Wait for the scheduled maintenance to start and check its update, which will report that "No components were marked as affected by this incident."

      This can also be replicated by creating multiple Maintenance tasks on the same component, resulting in the component being set to "under Maintenance" by 1 schedule, and the other schedule will report "No components were marked as affected by this incident."

      Expected Results

      List the component that is in maintenance, no matter what state it is in.

      Actual Results

      This is being reported in the update:

      No components were marked as affected by this incident.

      Workaround

      Currently, there is no known workaround for this behavior. A workaround will be added here when available

            Assignee:
            Unassigned
            Reporter:
            Beibei Song (Inactive)
            Votes:
            1 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: