Spiceworks Feature Requests

feature request Spiceworks Feature RequestsWasn’t sure what to do for a post this week so had a look on the community and settled with the feature request section… Don’t fully know where this post will end up but I’m just going to start writing.

Their are currently 564 feature requests some of which are just plain crazy others are really good. The feature request section on the community is one of the more recently overhauled parts off the community going from a mess of different requests to a cleaner meaner section. The Spiceworks staff can now combine multiple requests as well as mark them as implemented or closed. This helps them find out what people want quicker.

Checkout the feature request section here

It is designed to allow SpiceHeads to get the product they want by giving new functionality and changes a spice rating. The higher the rating technically the more change the feature request has off being implemented. Every member of the community can spice up and down requests helping Spiceworks work out what things are wanted.

Ok so that’s the boring intro bit done with now we can get into what the current top requests:

 

The current top 5

Spice Ratings pepper 16px3 Spiceworks Feature Requests

Name

625

Knowledge Base
We are working towards this feature. As of 4.0 you can create knowledge articles in the User Portal. In a future release we’ll add additional features to make this a fully functioning Knowledge Base.

254

Auto-archive devices after a time-limit
Is it possible to throw in a setting that lets computers offline for so many days/weeks/months etc to just disappear out of the database? Maybe set it as disabled by default and that way there aren’t any mistakes for new people?

239

Option to use MySQL or SQLServer DB Backend
After examining the system we found the major performance gains would be achieved in improving the web server in Spiceworks. We’ll investigate this feature once we’ve updated the frontend.

213

Multiple Client View
It would be interesting to be able to pull the data to their
implementation from their client sites. They can do this now by opening
firewall holes, accessing the application remotely but this is on a
customer by customer basis and require a lot of work to get the data
from many customers. A sync feature or an ability for one Spiceworks
deployment to trust another would be useful for them to view all the
data back at their location across customers.

209

Spiceworks Calendar
I’d like to see an extensive calendar/scheduling app in spiceworks. I understand that this would be a huge undertaking , considering the massive amount of integration I’m about to suggest.

I was rather shocked when I found out that having a Knowledge base was the top wanted feature. Currently it is just over twice as “hot” as the next feature request. The MySQL or MSSQL feature request is not one I’m a fan off, hopefully the 4.5 update to Apache will bring a lot of speed improvements and personally there are lots of new features I would love to see and various bits and bobs fixed before Spiceworks possibly open a can off worms by using a database like MySQL or MSSQL in which can be a lot more complex to manage, back and setup.

Seeing the above made me think about what are the underdog requests in which I feel people want but aren’t Spicing up.

 

My Most Underrated Request

So I had a look around and here is what I think are the 5 most underrated requests:

Spice Ratings pepper 16px4 Spiceworks Feature Requests

Name

127

Support for mobile devices – iPhone / Blackberry / Windows Mobile 
So this one is something everyone talks about but no one seems to Spice up. With things like Mobile Helpdesk by ObieOne appearing and lots of talks in the community. There have been many rumours of Spiceworks having talks with BlackBerry but nothing has come of this yet.

74

Convert an alert to a ticket
So this may not be something everyone would use but would prove very useful for change tracking, you could get an alert like “low disk space on x server” into a ticket related to a machine then this would be in your “task list” to be actioned and when actioned you could write up the change you made.

17

Attach tickets to multiple assets
There are many version off this like and Relate a ticket to multiple resources all in the lows but this is something ALOT of “Greens” (By greens I mean people with green still in their SpiceLevel) ask for all the time but never seems to get Spiced up, this maybe because there are multiple versions or just because not all the greens spice up feature requests.

14

Pushing Out Updates / Install Software Remotely
Spiceworks at the moment can access the WMI which should make pushing out update possible? There are lots of bits of software which will allow you to remote install like Purgos and a lot which allow you to push out updates but often they cost or need you to learn the install commands. If Spiceworks could use the community to input silent install commands for software then use this to allow people to deploy software it would be great.

8

Nudge person by name
Yes this is one of my requests but I feel it would be really useful for the “Community Pro’s” people like me, Jdorfman, Scott Alan Miller and the Spiceworks staff. Like twitter we would be able to use something like @akp982 which would nudge me to look at a topic. This would help get the right people to the right topics quickly. A generic one like @Spiceworks would call over a Spiceworks staff member but only be able to be used by people over x SpiceLevel to stop Spamming.

These are my most underrated and well probably just the things I really want but I tried to be far and pick ones that the community may feel are underrated.

 

There are LOADS of feature requests do Spiceworks read them?
Do Spiceworks action them?

groups Spiceworks Feature RequestsThis is a question that seems to get asked a lot on the community and in meet up’s like SpiceWorld, I don’t have any official word to hand but from the  many web and phone conferences I have had with Spiceworks I have a rough idea, here it goes.

There are currently about 564 requests for changes, so Spiceworks have to pick the ones they think will help the SpiceHeads the most.

Well there are many factors Spiceworks consider.

The main thing Spiceworks seems to look for is the things that will make it bit more special and useable as well as get them the most users. Things like work needed for plugins from vendors will take priority, ones like the vPro power manager plugin required a lot of backend work to be able to shutdown and start up machines.

image285 Spiceworks Feature RequestsIt then appears Spiceworks will try to hunt though the feature request section for at least 1 new feature to add to every major release. I’m not sure which conference the team mentioned this but one this year a team member stated they will always get one user submitted feature request in a major release (these being like the jump from 3.x to 4.x) but aim for more. This is something great to hear and this can be seen in the implemented page of feature requests one of the most recent and biggest feature request that has been implemented was the network map which has proven over time to be a great asset and one that really has brought new people in to the community.

Wasn’t really sure what to say so sorry that bits a mess, hope you get the idea? Maybe someone from Spiceworks will be able to drop me a PM or email and ill get the official word up icon wink Spiceworks Feature Requests

Checkout the feature request section here 

That it for now though, hope it wasn’t just the ramblings of a insane man

See you around the community

 

Please note: Spice Ratings were on the 24th December 2009 and can change daily.

8 Comments

LEAVE A COMMENT

Comments RSS Feed   TrackBack URL