We would like to see the ability to create "resolution" codes that would funnel up under custom states. Namely we would like to be able to add in custom codes for tickets that are canceled so we have detail behind that.
How To Influence Product Roadmap
Samanage is going through a significant growth period, both in terms of customers and employees. The product team has grown this year, which has allowed us to dive deep on some of the features we need to build as well as some of the challenges our users are facing. It’s important to us that you have the visibility into understanding “How do we know what to build?”
Customer Requests and Feedback
There are few things as critical as the feedback from customers when thinking about what to build. We treat customer requests very seriously, we track each request and see votes on requests from our customers and users. This enables us to view the most requested features with a few clicks.
There are nine status indicators we use with regards to feature requests. Please keep in mind that status of feature requests can change as our roadmap changes.
Current and Future Market Conditions
The IT service management landscape is constantly evolving. As a result, we have to be nimble in our roadmap. There’s no way we can set in stone what we want to build a year from now, as the conditions will change. We need to stay current and make sure that the features we build apply to today’s ITSM and ITAM landscape, but are flexible enough to meet tomorrow’s demands.
People often ask us why we don’t do feature x or feature y. For us, the key is ensuring that each feature we roll out is aligned with our vision for the product. We look to accomplish ITSM elegance through design, usability, feature delivery, and reduced complexity. This sometimes means saying “no” to things that others in our space may say “yes” to, allowing us to focus on the features that matter most.
Also, in an effort to increase transparency, please note that engineering time is devoted to:
*The more votes an idea gets, the more likely we are to consider it- but remember, sometimes things may sound simple, but in the backend are incredibly complex.*