Upgrade from 2.1 to 2.1.1 causes all tests carried out with 2.1 to show Non-Compliant in Results column

[duncangreene]

Describe the bug
Upgrade from 2.1 to 2.1.1 causes all tests carried out with 2.1 to show Non-Compliant in Results column.

cde42351-388f-4321-807b-b80794667513.mp4

To Reproduce
Steps to reproduce the behavior:

1. Have a 2.1 install with some previously complete (Compliant) results.
2. Upgrade to 2.1.1
3. See previous Compliant results now showing Non-Compliant.

Expected behavior
Result should be maintained between version upgrades.

Environment (please provide the following information about your setup):

• OS: Ubuntu 22.04.5
• Version: 2.1.1

Additional context
Witnessed on two separate machines that have been upgraded to 2.1.1.

[jhughesoti]

Are you able to provide reports for the same device in both versions? That would need to be evaluated to confirm where the issue is.

[duncangreene]

This is a Milesight UG67 tested under 2.1 and 2.1.1.

2.1
2.1.1

[jhughesoti]

Unclear on what issue this is trying to show as both of those tests have identical results.

[duncangreene]

As per the OP, the issue is that installing 2.1.1 over the top of 2.1 causes the 'Result' column in the UI to report Non-Compliant for previously compliant tests that were carried out using 2.1.

[jhughesoti]

This appears to be a bug with the UI after the introduction/remapping of the result/status fields in the report file.

2.1.1 Report section:

  "status": "Complete",
  "result": "Compliant",
  "started": "2025-04-07 13:38:25",
  "finished": "2025-04-07 14:00:03",

2.1 Report section:

  "status": "Compliant",
  "started": "2025-01-27 17:00:34",
  "finished": "2025-01-27 17:23:12",

UI is looking at result in 2.1.1 and status in 2.0 and does not account for missing result field prior to 2.1.

[duncangreene]

Just confirming for info that issue also present during upgrade from 2.1 to 2.2.

[jboddey]

This issue will be resolved in v2.2.1.