We are currently evaluating Logbook, and a question came up from one of our managers. Once Logbook goes live, is there a way to disable the current CRI module? Or do we have to remove permissions and disable tiles/reports?
Solved
Disabling CRIs
+2Best answer by sunasak
We have just done this. It was a big transition, due to people hating change 😀but it’s all done now.
- We removed the menu items for CRIs and Project Status, since we are doing all those in Logbook.
- We actually kept the tiles, but renamed them “Historical Risk” and such, so people still had access to what they entered before.
- We gave PMs a few weeks to transfer their CRIs to CRI logs, and it went pretty well. We had hoped for help from Planview but we had to do it manually. Teamwork makes the dreamwork!
- Our biggest hurdle was converting Power BI reports that used CRIs to draw the data from logs instead of the old way. It was a lot of work for the developer, but now that we have the most important reports up and running, it’s looking good.
I hope this helps. I probably forgot something. My job was updating lots and lots of internal training material.
This topic has been closed for replies.
+2We have just done this. It was a big transition, due to people hating change 😀but it’s all done now.
- We removed the menu items for CRIs and Project Status, since we are doing all those in Logbook.
- We actually kept the tiles, but renamed them “Historical Risk” and such, so people still had access to what they entered before.
- We gave PMs a few weeks to transfer their CRIs to CRI logs, and it went pretty well. We had hoped for help from Planview but we had to do it manually. Teamwork makes the dreamwork!
- Our biggest hurdle was converting Power BI reports that used CRIs to draw the data from logs instead of the old way. It was a lot of work for the developer, but now that we have the most important reports up and running, it’s looking good.
I hope this helps. I probably forgot something. My job was updating lots and lots of internal training material.
+2Hi
Thank you for sharing your experience! We’re also in the process of implementing logbooks and want to adapt our Power BI reports to the new setup but we haven’t received any documentation so far... Unfortunately, the Success Centre resources on this have been quite limited. Could you let us know where you found documentation for this transition?
Thanks,
Michal
+2+2Sounds like this is going to be a pain to migrate. We have a new wrinkle, we want to move Risks and Issues to Logbook, but we want to keep Changes in the existing CRI module. The Changes have the lifecycles built that follows are governance process around changes. So we will need to have users create only changes in the CRI module, but not issues and risks.
As far as Power BI they have released template for the Logbook reporting. We’ve decided we are going to create a separate report for now. That uses the template, plus data from AgilePlace and Portfolios via OData. I was hoping they would release details on how to connect as existing Power BI (the Portfolio Dashboard for example) to the Logbook tables.
Planview Customer Community
Already have an account? Login
Planview Customer Community
No account yet? Create an account
Login with SSO
Login with Planview Adminor
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
All Data Subject Access Requests (DSARs), and requests of “Do Not Sell My Personal Information” according to the CCPA, must be submitted through the Planview DSAR portal located here
Planview has appointed a Data Privacy Officer (DPO) to be responsible for overseeing our Privacy Management Program and related privacy compliance measures. DPO can be contacted at privacy@planview.com
Planview has appointed a Data Privacy Officer (DPO) to be responsible for overseeing our Privacy Management Program and related privacy compliance measures. DPO can be contacted at privacy@planview.com