When two or more people are reviewing at the same time in shared mode, some issues may disappear depending on the combination of certain operations and save timing.
Target version
Lightning Review 1.8 to 2.5.0
If you are using 2.5.1 or later, you can restore the deleted issues by following the steps in the following link.
Phenomenon
We will explain the prerequisites and the operations that cause the phenomenon.
-
Prerequisites
- The review file is in a shareable state (shared mode).
- Two or more users open and operate the same review file.
-
Target operation
The problem will occur if users A and B perform the following operations in the order below.- User A: Add one comment directly under the document and save it.
- User B: After saving the review file, perform any edit operation and save it.
This applies not only to adding/updating comments, but also to operations that change the contents of the file, such as changing the review name on the overview page.- User A: Save after performing one of the following operations.
The final save operation will reflect the change in 2 in the review file.-
(a) Click "Create outline from document".
-
(b) Open the target file from the arrow mark when no outline has been registered.
-
(c) After changing the "Document related links", update the outline tree.
After updating, select "Yes" in the dialog box that asks whether to reflect the changes in the outline tree.
-
(d) Move the issue to another outline node or document, then move it back to the original document.
When you perform the above operation, all issues registered in the document for which step 3 was performed will be deleted.
In the figure below, if step 3 above is performed on "XX Function External Specification.docx", the 17 registered issues will disappear.
How to recover when a problem occurs
If the issues disappear, it is difficult to recover (return the issues) using Lightning Review alone.
However, if the review file before the issue occurred remains, you can recover it by following the steps below.
-
Open the review file before the issue occurred.
-
Start Lightning Review and open the file where the issue occurred.
-
Use the following function to copy and paste only the issues you need from 1 to 2.
-
Save the file in 2.
- Network folder: Get the backed up file
- Configuration management tools such as Git and SVN: Get the most recent version of the file from the history
Workarounds for the problem
There are the following workarounds depending on whether or not you use the sharing mode of Lightning Review.
When using the sharing mode
In this case, during operation, please perform the following operations when performing the "target operation" of the phenomenon.
| No | Target operation | Workaround |
|---|---|---|
| 1 | Save the review file | Perform this when other users are not editing at the same time. (You can check whether users are editing in the "Review sharing settings" dialog.) |
| 2 | (b) When the outline is not registered, open the target file from the arrow mark | Create a dummy node under the document in advance.  |
| 3 | (c) After changing the "Related Links for Documents", update the outline tree | Select "No" in the dialog box that asks whether to perform outline analysis.  |
| 4 | (d) Move the issue to another outline node or document, and then move it back to the original document | Save the review file before moving it back to its original location. |
If you are not using shared mode
This problem will not occur if you uncheck the following.
�@
However, this may cause operational problems, such as multiple members being unable to post issues at the same time.
Please implement this solution if you can avoid the problem using the following method.
- Register issues in separate review files and later combine them into one.
- Register review files in GitHub/GitLab and use Git functions to merge issues.