Status changes made in versions older than 2.0 may not be reflected in 2.0

Affected version

Lightning Review 2.0 or later

Affected function

This occurs in the following screens/dialogs.

• "Status" on the "Overview" page
• "Review workspace folder" grid on the "Start" page
• "Review workspace folder" grid in "Review Explorer"

Conditions for occurrence

Change the status in a version older than 2.0 for a review file that has been saved in Lightning Review 2.0 at least once in the past.

This refers to adding a status, changing/deleting the name, and changing the selection state.

Phenomenon

When the review file in "Conditions for occurrence" is opened in Lightning Review 2.0, the following occurs.

• The status added in a version older than 2.0 is not displayed.
• The status before editing (last saved in 2.0) is displayed.

Specific example of the problem

1. Create a review file in Lightning Review 1.8 (environment ①) and define statuses A, B, and C.
2. Open the review file in "1" in Lightning Review 2.0 (environment ②) and add status D.
3. Open the review file saved in "2" in environment ①.
   At this time, the statuses A, B, C, and D are displayed.
4. Add status E to the review file opened in "3" and save it.
5. When the review file saved in "4" is opened in environment ②, the status added in 4 (E) is not displayed.
   Only statuses A, B, C, and D are displayed.

Workaround

This restriction occurs when the status of one review file is edited in different versions of Lightning Review.
Please make sure that your team or organization uses the latest version of Lightning Review.