Missing features

Hey @alleneagle we’re sorry you’re having a less than stellar experience right now. I’ve escalated this to your PSM and to our executive team to take a look and see if we can schedule a refresher to show you where the functionality your looking for lives. 
 

Thanks for being a part of our Community and sharing your thoughts. We’re really happy you’re here!

Hi @alleneagle 

When we redesigned Roadmaps, we had a bug where we lost the ability to move assets from an Initiative to a separate quarter. We’ve now resolved this!

Our main goal in redesigning Roadmaps was to improve simplicity wherever possible without sacrificing functionality. One significant change we made is that Initiatives are now all confined to a single quarter, but you can easily select assets from a workstation replacement Initiative in Q1, for example, and create a new workstation replacement Initiative in Q2 with those assets. The main reason we did this is it makes it easier to track projects that span across multiple quarters.

We understood that use cases like the example given are common, so we also invested in improving the ability to filter and add assets to an Initiative from within the Initiative itself.

We’re continuing to invest in this area, so I’d like to hop on a quick call to gather more feedback and any ideas you may have on improving Roadmaps further. I’ll drop you an email!

-- Andrew, Product Manager (Lifecycle Manager)

This was a HUGE feature that is now missing and very frustrating. @Andrew Day the “simplicity” of the redesign is now significantly more time consuming - it takes a very long time now to split these off into quarters by needing to create a whole new initiative. I’ve brought this up with @Colin Roche a few times and we’ve walked through the new process together: it’s miserable. 

I’m not certain I’ll be renewing Lifecycle Manager this year with this feature now missing. 

I ended up only using Scalepad to sync data from my RMM, let it add the important information I needed such as the age of the machine and warranty. Then I export that to a spreadsheet with some simple formulas that gave me a breakdown of which computers are due for replacement based on our desired lifecycle age (3 years in our case) and which year/quarter they are to be replaced. I was then able to determine yearly/quarterly budget based on the results for the next 3 years.

@pdxcomputerpro I sent an email over to chat about your feedback.

@alleneagle we’ll have an elegant solution for that soon. Stay tuned. :)