360 Review - Updating someone else's course

In the same vein as this, it would be extremely helpful to be able to publish anyone's review360 course in my organization to Rise360. This way there is only one controlled version in review that is linked to Rise. Right now I have to download the storyline file from my collaborator, publish in my review, then link vs just linking the review file they have already published. 

Hi Kyra!

Thank you for sharing this with us! It sounds like you're looking for collaboration tools in Review 360, such as a team dashboard, perhaps. I'll make sure to share this request with our team!

Hi Team

I have exactly the same issue as written by Matt McGuire 3 years ago. Is there any advice? Or could I republish the course and transfer all the comments (87) over (copy paste with a note saying who made the comment)...a quicker fix would be much clearer and mush appreciated. Cheers Oriel

This is an ongoing issue for my team as well. Part of our maintenance process is course owners requesting their courses be published to Review 360 so they can submit required updates. However, the ISD who publishes the course to Review 360 is rarely the one who has bandwidth to make the changes however many days/weeks later. So we end up losing the comments when the editing ISD republishes and creates a new link for course owners to approve the changes. Even if we export the comments and send them to the reviewer as a PDF or spreadsheet, it's immensely cumbersome. There should definitely be a way to import comments.

Has this been put on a list for immediate future improvements?  We had a colleague leave and another one is going out on a FMLA leave and we dont want to lose the comments or have to export the files for each course. 

Please let me know!  Thanks!

Hello,

We still don't have an update on the Review 360 folder improvements requested here, but you can check out which features are being worked on by visiting our roadmap. Here's how we handle feature requests for you reference. We'll let everyone here know as soon as we have an update on the requests!

I'm adding my name to the list here on being able to update a previous version created by someone else. My colleague is on maternity leave and I'm updating projects she started, so this feature would help us enormously! I see its appearing on the Roadmap, so am keeping my fingers crossed it won't be long!

I would like to chime in as well.  I was just on vacation for a few weeks and my colleague and I have been working on 7 modules, but now she had to republish to a new link for the ones I developed.  If we are all on one team, updates should just go to one central Review link repository.  This can truly become a version control nightmare.  We are keeping them straight by labelling the newer versions with dates and initials.

I might as well add my comments as well. I'm currently working on a Rise course that someone else created and I'm making some tweaks for release 2. He still has ownership, so when I published, I got a new review link. OK, not the best experience, but I thought, we'll just say that for release 2, this is the new review link. However, when I made changes and then went to republish, it won't let me publish to the new review link that I just created; it forces me to create a brand new link. That's insane. Even though I give my SMEs the new link (and then the new, new link), they don't understand that it's changing each time and comment that they don't see my changes. 

Please, please raise the priority of this ticket.

I know our team would also like this as often we have multiple IDs working a single project.