+1
I just had this happen and could not find a workaround without copying the SQL out and back into a custom SQL report and adding portstatus (operationalstatus) by hand.
+1
I just had this happen and could not find a workaround without copying the SQL out and back into a custom SQL report and adding portstatus (operationalstatus) by hand.