http://brainstorm.ubuntu.com/item/8881/
Instead of marking bugs as "not an idea" I propose that the brainstorm developers export all the "non ideas" which are marked as bugs to be exported as a CSV file and FTP'd over to the Ubuntu bug tracker. Once there, the bug tracking database should import the data and be listed as a bug.

Since brainstorm and all other ubuntu logins will be universal soon, this will integrate nicely.

I just think its a lost cause to mark stuff as not an idea, and then do nothing with it. All that data just going to waste, and then telling the user to post it to the bug database. It just isn't efficient, and it is causing bugs to go unreported. One of the biggest problems with Ubuntu (and the Linux community in general) is that bug reporting is not taken seriously when reported by an end user. Most of the time it is because the end user reports it to the wrong place. This is why Brainstorm should allow this feedback from end users to flow freely to the bug tracker. Because brainstorm is a much friendlier feedback loop for end users than bug databases are.

[76 votes] Solution #1: Auto-generated solution of idea #8881


]]> en-us Wed, 21 May 2008 03:02:18 +0000 Fri, 24 Jul 2009 11:48:56 +0000 QAPoll module http://brainstorm.ubuntu.com/idea/8881/
-1]]> Wed, 21 May 2008 07:45:05 +0000
+1]]> Wed, 21 May 2008 10:36:10 +0000
You seem to be of the philosophy that known good bug reports should be left ignored, and the end user who reported it should just be given a slap on the wrist. This is a preposterous notion.

You may think its simple chores you and me can do but guess what. All the power users have reported all the bugs they know about. If they didn't, then they aren't a power user. Most of them, developers choose to either ignore or give them low low priority. Then there are the end users, who are simply left out in the cold completely and none of their feedback ever makes it to a developer.

But reporting should be simple. You go to forums, brainstorm, email lists, everything, and you will find bug reports which are ignored and not reported to the tracking database. But they are forms of feedback that came from an end user, who does not know all the policies in place. And they are simply ignored even though we all admit they are legitimate bugs.

There is no reason that an automated system could not be put in place to import brainstorm ideas as bugs. Plain and simple, it could be coded in 10-15 minutes and QA'd in less time than that.

Guess what the percentage of people who post to forums, brainstorm, etc... who are told "you should not post this here, post it to the bug tracker blah blah blah..." or just simply ignored all together. What percentage of those people will actually go to the bug tracker and post the bug? probably maybe 1% if your lucky.

]]> Wed, 21 May 2008 22:33:39 +0000
mp3phish: As far as power users reporting all of the bugs they know about - not true. Most users, power or otherwise, will get to the point where they feel reporting bugs isn't worth their time - either because the bug isn't that annoying, or it's easier to fix it for their own system than it is to try and get the Ubuntu devs to fix it. However, this isn't an argument against your idea, because the power users at this threshold aren't going to be reporting these bugs regardless, unless someone comes up with a way to have the Ubuntu devs magically resolve all problems which are reported within just a few weeks of them being reported.

However, the automated system you describe would only be that quick to develop if the interfaces between Brainstorm and their bug tracking system are similar enough. There is no good reason for them to not be - however, unless they were developed in relation to each other, there is no good reason for them to be. That having been said, it shouldn't take more than a few hours, even with wildly different interfaces. In any event, I'd want to put it through at least an hour of QA, probably more.

I think another part of the problem is that the systems don't link to each other.]]> Fri, 06 Jun 2008 19:07:32 +0000
Idea #10134: Bugs that are "not idea" get automatically forwarded to Bug Reporter (Launchpad).
http://brainstorm.ubuntu.com/idea/10134/

Idea #10070: Ubuntu could process suggestions for packaged programs (be a suggestion portal).
http://brainstorm.ubuntu.com/idea/10070/

Idea #11109: Package Requests for repos and Bug Reports - Appalling state of affairs.
http://brainstorm.ubuntu.com/idea/11109/]]> Fri, 08 Aug 2008 02:14:57 +0000
To an end-user - they will not necessarily have the knowledge to log a bug with all the information that a developer wants. Instead - they will be thinking in terms of " has failed".

End users on most cases don't know or care what part of the distro has blown up. All they know is that it's blown up.

I've taken a look at the Bugs section of Launchpad, and while it is adequate and actually probably quite good for info exchange between developers... how about making it easier for people to raise initial incident tickets by means of a decent form or 3?

Before you direct me to the Questions section.. again.. this is not all that easy for the end-user.

Now - where you think "bug", I think "Desktop Enhancement Request Form" (from work). However, this is used by developers. Not when capturing Enhancement requests from end-users...

It's also been said.. that if something is going on upstream.. why should an end-user know or have to chase themselves? They will go to the people who support their install...

Just thoughts..
]]> Thu, 06 Nov 2008 23:06:38 +0000