We need a category for reporting problems specifically
-
@deckingman said in We need a category for reporting problems specifically:
@gnydick What you are proposing won't work and here is why.
The Duet team know what would help them. I've met them all and can confirm that they are all fully grown up adults, more than capable of making their own decisions.
To this end, they have tried to get users of these forums to do things which would make it easier to solve their issues. A fairly recent example is this sticky https://forum.duet3d.com/topic/5909/guide-for-posting-requests-for-help
All things described in that topic should be mandatory. There shouldn't be any free-form threads when dealing with problems.
-
@edgars-batna said in We need a category for reporting problems specifically:
All things described in that topic should be mandatory. There shouldn't be any free-form threads when dealing with problems.
Exactly so. But how do you enforce it?
It's just human nature that some people don't read or follow written instructions. Maybe what is needed is that people have to fill in some sort of form whenever a new thread is started? That might work but there will always be people who jump in on an existing thread and say "I have a similar problem" but those people may not be using the same hardware or firmware or whatever. So then it becomes necessary for users to fill in a form whenever they make a post, which just isn't going to work.
-
@deckingman Yes, a form. Something like a JIRA bugtracker, Bugzilla, Redmine, etc. There are various tools around that are used for software projects that would apply here quite well. Github is not ideal as it's too free-for-all and applies to software only, the forums being a total one-shot-kill deathmatch in comparison.
Maybe the forum software can be extended to support mandatory fields... but why reinvent all the wheels.
-
@edgars-batna said in We need a category for reporting problems specifically:
Yes, a form. Something like a JIRA bugtracker, Bugzilla, Redmine, etc.
dc42 has already ruled out a "bug reporting" category.
Structured bug reporting is fine for programmers and beta testers and the like, but for end users it is not going to be pretty.
-
@fcwilt I don't object to first come, first serve. I object to dc42 having to scour all categories equally. Even if the one category was abused, it would still be less than having to worry about missing something hi-pri because it was buried somewhere innocuous.
-
@gnydick said in We need a category for reporting problems specifically:
@fcwilt I don't object to first come, first serve. I object to dc42 having to scour all categories equally. Even if the one category was abused, it would still be less than having to worry about missing something hi-pri because it was buried somewhere innocuous.
Hmm...
I may have made a invalid assumption. I was thinking that dc42 could view them not by category but by date so it would just be a matter of starting at the oldest post not yet viewed and working towards newer posts.
I will have to ask him.
-
@fcwilt said in We need a category for reporting problems specifically:
starting at the oldest post not yet viewed and working towards newer posts.
That would be the unread posts view. That's what I use anyway.
-
@phaedrux said in We need a category for reporting problems specifically:
@fcwilt said in We need a category for reporting problems specifically:
starting at the oldest post not yet viewed and working towards newer posts.
That would be the unread posts view. That's what I use anyway.
Thanks for that info. It seemed likely there was a way.
Frederick
-
Ahhhh, that's handy
-
I use the unread posts view. When I am short of time, I ignore posts whose titles appear to relate to printer construction, print quality issues and similar issues that are not obviously related to the Duet, its firmware and configuration.
