Last modified: 2013-06-18 16:06:16 UTC
It is plenty clear how to submit a bug, but it is far from clear how to submit a request. Perhaps a web page betwenn "Enter a new bug" and "Reports" entitled Feature Requests, linked to a bug report template with "enhancement" as severity already selected could be added to the main webpage.
Yes! Exactly! Other mediawiki sites link here as the place to send future feature suggestinos - where do I submit those? I have an idea - OK maybe it's not that great, but anyway lots of sites like to have a "Featured Article" on their front page and it would be nice to be able to have a special "Article" template thing that would return all the content in an article ... so you'd put on your front page (inside a table presumably) {{Article|Name of article}} - so that way changes made to featured articles appeaer on the main page immediately. Or perhaps there's something that already does that ... I'm messing around with a wiki I've set up just to learn how it all works (localhost only right now - sorry people) how do I do that? I'm not sure whether this is a feature request or a help request, you know?
Most sites which have that either transclude the whole thing, or a template containing selective text. It's possible to include the whole content of an article already. Also, please keep feature requests one per bug.
I agree on the fact that it is not clear how to submit the various things, like bugs, patch, feature requests. And there is no documentation (to the best of my knowledge of course) on this topic. I had to ask on IRC, and check the list of bugs to copy what was already done. I think the right solution is to update the documentation linked in the very first page seen when one submits smth.
For an interesting example, see bug 4217. It's not broken, so it's not a bug. It's not a feature request either. But I still think it's a valid suggestion.
It also makes searching for either a bug or a F.Req (which people should do before submitting them again) more difficult by needing to browse through the common list. Splitting them would be preferable. On a similar but unrelated note, I also don't really see the need to log in and create an account to submit these incidental things which may only occur once when somebody has one bright idea or notices the uncommon bug.
(In reply to comment #5) > On a similar but unrelated note, I also don't really see the need to log in and > create an account to submit these incidental things which may only occur once > when somebody has one bright idea or notices the uncommon bug. Your suggestion has been noted as bug 12179.
Bulk-assigning open BZ issues to Fred.
I have added a couple products to submit tickets for Suggestions and Feature Requests on MediaWiki and Wikimedia. Let me know if there is anything else.
IMHO this makes things more confusing, not less. Now we've got 3 Mediawiki components and 3 Wikimedia components and I'm trying to figure out the workflow in between them. Are we expecting users to submit under the new products and we (ie: devs, bugzilla regulars, etc) will recategorize them into their appropriate areas (ie: Mediawiki -> enhancement)? I think it's a needless step in the process and creates more work for us with marginal benefit to the end-user. Two things I think can fix this: A) Change the "Enter a new bug" text to say "Enter a new bug or feature request" B) Change the landing page from there to be more intuitive, maybe providing pre-filled links like "Mediawiki Feature Request" or "Mediawiki Bug" with the appropriate severity already set.
Agree - this is much worse. Creating more products is counterproductive - as if bugzilla isn't already an incomprehensible labyrinth for new users already. Some pseudo-wizard function for pre-filled forms would be great. If that's not possible, then documentation & links to appropriate places on the landing page would be second-best.
Unless anyone has any huge desire to keep these around, I'd like to remove them (at least for now). This process does need improvement, but this isn't the solution and I'm open to any ideas people might have. Right now, they just grab a few bugs a week that end up getting assigned elsewhere anyway.
It's been a week, went ahead and removed them. Back to the drawing board for fixes to this problem :)
Bulk assign Bugzilla related issues to pdhanda: current maintainer
Bugmeister is the new Bugzilla maintainer and default assignee.
Resetting to default per bug 37789
Feature requests = set the "Severity" field (part of "Importance") to "enhancement". If this is not clear than the question is where to document it. Any proposals? [I've used and maintained Bugzilla installations with separate products for bugs and feature requests and I agree it's confusing (plus two products to query for, as there is a thin line between bug and feature sometimes).]
(In reply to comment #16) > Feature requests = set the "Severity" field (part of "Importance") to > "enhancement". > If this is not clear than the question is where to document it. > Any proposals? Ping? > Some pseudo-wizard function for pre-filled forms would be great. That would require fixing bug 36762 I guess.
Unfortunately closing this report as no further information has been provided. marudubshinki: Please feel free to reopen this report if you can provide the information asked for. Thanks!
