This ticket is related to a bug identified in the process of resolving Ticket #6217.
The historical analyzer range data of an ended component appears alongside new analyzer range data within a newly created component, as per the image below:
Similarly, when checking the old component that was ended and the corresponding ended analyzer range, the new analyzer range appears alongside the old range, as in the image above.
Steps to Recreate the Issue:
Create new components for each of the 5 component types with analyzer ranges: ORIS 3, 6A (NOX, CO2); ORIS 628, 1GTA (O2); ORIS 298, 1 (HG, SO2). Steps taken:
End existing component, analyzer range. Start new component / analyzer range on following hour.
Export to JSON, revert record to official, import new JSON, and check for changes in UI.
New component will show list will show two analyzer range entries, the old range which was ended, and the new range that was added.
Similarly, if you check the old component which was ended, it will show both the old analyzer range and the new analyzer range created for the new component.
Expected Resolution:
New components for systems should only show new analyzer ranges, while old components should only show old analyzer ranges, not both.
annalbrecht
commented
3 weeks ago
This ticket is related to a bug identified in the process of resolving Ticket #6217.
The historical analyzer range data of an ended component appears alongside new analyzer range data within a newly created component, as per the image below:
Similarly, when checking the old component that was ended and the corresponding ended analyzer range, the new analyzer range appears alongside the old range, as in the image above.
Steps to Recreate the Issue: Create new components for each of the 5 component types with analyzer ranges: ORIS 3, 6A (NOX, CO2); ORIS 628, 1GTA (O2); ORIS 298, 1 (HG, SO2). Steps taken:
Expected Resolution: New components for systems should only show new analyzer ranges, while old components should only show old analyzer ranges, not both.