Update 14th May 2020 11:30 UTC: These issues have been resolved and the functionality has been re-enabled.


Chorus is not reporting the correct change labels when you publish your specification and compare it to an earlier version. Two scenarios have been identified. This article links to a detailed explanation of those scenarios.


Whilst this is being fixed NBS has disabled the compare function on all publishing routes. We have also disabled the save to publish history when publishing a selection of the specification. 


This means that when you publish your spec you will temporarily not be able to compare it with a record in your publish history.


We apologise and are working hard to fix it.


We will be posting updates and answering queries on this issue in the Known issues forum. Please follow this if you want to receive update notifications.


Short explanation

  1. Comparing against a publish history record saved when a selection of your spec was chosen - will report sections/systems as being REVISED even when they have been UNCHANGED.

  2. Parking (and unparking) whole articles or clauses - will result in the section being reported as UNCHANGED when it should be showing as REVISED.

 

Detailed explanation

Issue with reporting changes when publishing a selection of your specification

Issue with reporting changes to parked articles/clauses


How this impacts your specification

If you compare the spec you are publishing now with a record in the history affected by these issues, you will see change labels saying REVISED or UNCHANGED which may be incorrect in certain situations.


The content of your specification is unaffected. This issue relates to the reporting of how the document has changed.


Publish history records that were saved since 18th February 2020, when saving to the publish history was introduced, will give inaccurate change labels.


We do not recommend that you compare against these records because you will get potentially inaccurate change labels in the spec.


What we are doing about it

  • NBS has disabled the compare steps when you publish the specification in full. We are still allowing a publish history record to be saved for the full specification as this may be useful to see the timeline of the project. Please note until we have corrected the revisions logic, comparisons against these records will give potentially inaccurate labels.

  • NBS has disabled the save to publish history and compare steps when you publish with a selection of the spec chosen. This will prevent any further instances of this issue being saved to your publish history.

  • Work is underway to correct Chorus so future publish records will be accurate.

  • We will re-enable this functionality once this is resolved.

  • We will be displaying which records in the publish history have bee affected so you know to avoid comparing against the in the future.


We apologise and are working hard to fix this.


Here is a link to the Known issues forum where we will be posting updates and answering any queries you might have about this.