Comments disappeared in Review

Why would a new "version" in Review360 remove comments?  They should persist across the project, not the version.  You might have comments you address in one build, and then another set of comments to address in another build. If the comments are tied to each Review360 "version" (publish) that is a problem.

Upon further inspection of our own dynamics, the case of mysterious vanishing comments, was actually a user action.  They published to Review360 as a NEW ITEM. Even though the course name was the same "Topic A & B v1", Review360 in fact created two review objects with the exact same name. Depending on which you clicked on, the comments were there, or not.  Perhaps this is not the mysterious behavior others alluded to, but this explained the vanishing act.

Hi Don,

Thanks for following up on this thread with what you found! I'm glad to hear that you were able to locate the course that the comments were left on. If you need further assistance, please let us know and we'll be happy to help!

Hello,

I would also like to state that I am currently experiencing this issue as well. A client and I went through a project together, adding comments to the review link. However, now the notes are nowhere to be found, including alternate versions. I only wanted to add my voice to this thread to increase the urgency of getting this issue resolved.

Thanks,

Had the same issue: had about 12 comments; fixed the issues from a Rise Course, republished to Review and did a versional.  All the Comments were gone with the new version.  i checked the feedback repository and checked to see if they showed up in the Resolved; they did not.

I had the same think happen yesterday on a different course. The publish to Review from Rise did act a little differently and on first try it didn't even recognize the previous course version. It prompted as if it were a new course (RISE.)  

I shut down, and tried it again, then the option to do a version appeared.  I believe it was the result of changing the title.  In Rise, I tagged my Rise Course with a special character, as I do to distinguish versionals (same process I do in Storyline360.)  However, I did change it back to the original title - exactly.  I believe this is what triggered Rise to Review publish to think it was a new course (Probably a tracking cookie).  

When I shutdown all browsers and the Articulate 360 window, relaunch, and go back into RISE, that is when I had the prompt to publish to review a new or version. 

So I caution to not tag titles as versions, even though you change it back.  It could have bad consequences.  I think this is what wiped out my previous comments, though I can't be sure, but it does sound plausable.

Hope this isn't too confusing.

I am experiencing the same issues, very frustrating.  I am the owner of a  Rise course where Reviewers placed their comments.  I made edits to the lesson text, then went to Share / Publish new version / Publish a new version of an existing item, carefully making sure I select the correct existing item.  This updates the Rise content, but does not show the existing comments from previous publishes.

This statement is from the User Guide Luciana posted at the top of this conversion -  "Comments roll forward with each new version, so you’ll see comments for the version you selected and all versions"

The comments are not rolling forward.  Please provide instructions on how to have them present in each publish.  The steps in the User Guide are not working. 

I'm having the same issue, the comments disappeared after I removed the current question bank and inserted a new one. I suspect it is because the comments were linked to the question bank. However, normally when I remove/edit a page that has comments on it, the comments still appear, but they are listed under 'removed slide' or something like that.

I can still go back and see the comments on the previous version though, luckily.

I, too, am still experiencing this issue as described above by numerous users and am on a crucial deadline that is costing me time I cannot afford.