Better feedback on feature requests posted here....

[dkightley]

This thread is a follow-on from this thread relating to software development: viewtopic.php?f=23&t=5668

There is a frustration amongst users who read this forum that there's no feedback regarding all the new feature requests and bug reports that are posted on this forum. This has led to doubts that the software is being developed....and JasonCS has posted on the above thread that indeed the software is still being developed, and that feature requests we post here are read and taken into account, etc. With one question hopefully answered to the satisfaction of most, there is still an issue with a perception that requests we post here are being ignored.

One possible solution would be for the developers to provide some form of regular feedback.....say on a weekly basis.....on the posting in both of the user feedback sections. To minimise the effect on other work, I don't think we would be wanting anyone to engage in a conversation on the relative merit of each request, but to simply provide in the form of a comment their initial thoughts on the perceived benefits, the likely ease or scale of effort to code the request, etc.

Let's have something.....not total silence as we have at the moment. I'd prefer someone to say "Sorry, that's not the sort of change we would want to include." or "A good idea, but it would affect the slicing speed." or "What a good idea. We may add that to our list of changes to consider for inclusion in a future release." rather than there be a total silence....which currently is giving the feeling that what we, the loyal users, are doing to try and help the software improve is a waste of our time! That;s certainly how I feel!

Then....as I think happened with v3.0....it would be nice to see a comment on each request that actually made it into the release....and possibly a note on any requests that are not likely to be dealt with.

Hopefully, ohers will be able to refine and develop my initial idea.....

[JohnOCFII]

Let's have something.....not total silence as we have at the moment. I'd prefer someone to say "Sorry, that's not the sort of change we would want to include." or "A good idea, but it would affect the slicing speed." or "What a good idea. We may add that to our list of changes to consider for inclusion in a future release." rather than there be a total silence....which currently is giving the feeling that what we, the loyal users, are doing to try and help the software improve is a waste of our time! That;s certainly how I feel!

I know it's uncommon in the (non-open source world) to comment on future developments in detail, but if the team could even indicate on a few threads that something is "on our roadmap" that alone would be useful (and still noncommittal as to timing, etc.).

John

[TMeyer]

A good example for a feature system is at autodesk's so called IdeaStation:

https://forums.autodesk.com/t5/ideastat ... /idb-p/125

There users can post their ideas, get +1 / -1 (Kudos) from other users (and of course autodesk team as well) and the possibility to write some additional words. Autodesk team then marks these threads with icons like:

'Gathering support'
'Future consideration'
'Accepted'
'Implemented'

So the users can immediately see what happens with their idea.
Such feature is missing on your website and this is the reason why users feel alone.

[dkightley]

After all the fuss over the question "Is S3D still being developed?" in the above linked thread....the first thread in this section that has actually resulted in a response from the S3D development team, I am really disappointed in the total disinterest by users of this forum in the first chance we have ever had to influence how the S3D team interact with users.

We were asked for our thoughts on how the development team could provide any form of feedback on requests for new features.......and the overwhelming response is total apathy!!!!

I don't really know why I bothered!

[Lagbert]

Most forums have a polling capability. It would be nice if the developers would poll the users on which features should be prioritized. Maybe a monthly poll with ideas gathered from the suggestions in this section.

I think one of the biggest issues with the suggestions forum is it really needs to be broken up into several sub-forums

1. Printer support requests
2. API/Software support requests
3. Slicing methodology requests
4. User Interface (UI) enhancement requests

If we as a community prefaced our post with

Printer, Software, Slicing, and UI it would make sorting through and finding suggestions to rally around much easier.

[TMeyer]

Hi,

and again - silence...

@Simplify3D team:

1. What about a better feature request tool?
2. What about a schedule for implementing the features requested by users?
3. What about an update to 3.2?

[dkightley]

and again - silence...

In this case I must suggest that the greatest silence has been from users of this forum.......

We were asked for ideas on how communication could be improved....and look what the response was!

[tenaja]

Ok, Doug, I'll contribute.

I do NOT want more sub forums. We have plenty of subs for the amount of traffic here.

I think one interaction from the devs would be nice, and that is a thread response with IMPLEMENTED added to the topic when appropriate.

Anything other than is bonus.

The only bonus I'd appreciate is a comment in threads if they might make an attempt at implementing it, perhaps "hey, nice idea", but not much more.

I hate when devs waste time defending themselves for trying to come up with a polite way of saying "that's a stupid idea."

[wfcook]

I would suggest moving the bug/feature section to a different type of site, namely the YouTrack system from MyJetBrains. I have used it heavily working with McNeel, the developers of Rhino3D. You can see their system at http://mcneel.myjetbrains.com/youtrack/dashboard

It works very well.

[TMeyer]

@dkightley:

Silence from users?!? Did you read my post from Mon Aug 29, 2016 2:32 am? Is this silcence?

No reaction from S3D Team