|
luiscubal
|
|
Reply #16 Posted on: July 08, 2010, 06:15:09 am |
|
|
Joined: Jun 2009
Posts: 452
|
Yes, it now correctly detects that I'm logged in.
You should now implement bug categories, like "Bugs", "Feature Requests", etc. Also, you could have "recommended" tags, such as "regression", "wanted-r5", "blocking-r4", etc. Think of it as some sort of autocomplete system. You could also have bug templates. For instance, when creating a new bug, it'd show in the content box "Steps to reproduce", "Expected result", etc. I think that's pretty much the essential for now.
|
|
|
Logged
|
|
|
|
Josh @ Dreamland
|
|
Reply #17 Posted on: July 08, 2010, 08:44:02 am |
|
|
Prince of all Goldfish
Location: Pittsburgh, PA, USA Joined: Feb 2008
Posts: 2950
|
Suggestions are given very low priority. I like the recommended tags idea. Maybe in a large cluster or something like a lot of sites do, with more frequent tags in larger typeset. The template thing only really applies to bugs. A trend seems to be the ability of people in general to propose a solution. Canonical and several others I've observed lately seem to have an answer proposal box at the bottom of each bug report (at least those given attention).
a2h, I'm amazed at how well this all works together. Great job!
|
|
|
Logged
|
"That is the single most cryptic piece of code I have ever seen." -Master PobbleWobble "I disapprove of what you say, but I will defend to the death your right to say it." -Evelyn Beatrice Hall, Friends of Voltaire
|
|
|
luiscubal
|
|
Reply #18 Posted on: July 08, 2010, 10:53:07 am |
|
|
Joined: Jun 2009
Posts: 452
|
You could do much more with the tracker. I've suggested what I thought was the bare essential to make it usable.
Additionally, you'll need: 1. The ability to vote for bugs 2. The "email me when this bug is modified" checkbox (off by default) 3. The "Assigned To" field 4. Division in components(is it a bug in the parser or in the drawing code?) 5. Filters (show only Linux bugs, don't show Linux bugs, etc.) 6. Associate bug with URL(such as forum discussion, game that exposes the problem, etc.) 7. Submit files (test cases, patches, etc.)
THEN, it'll stand a chance to be a good tracker. But I believe my previous suggestions are more important.
|
|
|
Logged
|
|
|
|
Josh @ Dreamland
|
|
Reply #19 Posted on: July 08, 2010, 11:33:45 am |
|
|
Prince of all Goldfish
Location: Pittsburgh, PA, USA Joined: Feb 2008
Posts: 2950
|
General: I believe a2h has or was going to add categories, certainly. Perhaps some will want to have a separate category for suggestions. It'd probably be good if he let the intermediate user (as in, whatever we are to Simple Machines: not the creator, not the end-end-user) change the labels of each severity. That's just if he wants to put it out there for the public, as I know is his intention.
1: Vote for bugs. I assume you mean "This affects me, too!", in which case, yeah. Good idea. 3: There is an Assigned to: field. 6: That's kind of silly; why not just paste any concerned URLs into the body of the bug report?
I like the idea of and have no further comment on suggestions 2, 4, 5, and 7.
But personally, I'm happy with it right now. So he can take his sweet time on that extra glittery stuff. As long as I can mark a bug "solved," which I've not yet been given a chance to test.
|
|
|
Logged
|
"That is the single most cryptic piece of code I have ever seen." -Master PobbleWobble "I disapprove of what you say, but I will defend to the death your right to say it." -Evelyn Beatrice Hall, Friends of Voltaire
|
|
|
|
notachair
|
|
Reply #21 Posted on: July 08, 2010, 08:37:15 pm |
|
|
Definitely not a chair
Joined: Feb 2008
Posts: 299
|
Yes, it now correctly detects that I'm logged in.
You should now implement bug categories, like "Bugs", "Feature Requests", etc. Also, you could have "recommended" tags, such as "regression", "wanted-r5", "blocking-r4", etc. Think of it as some sort of autocomplete system. You could also have bug templates. For instance, when creating a new bug, it'd show in the content box "Steps to reproduce", "Expected result", etc. I think that's pretty much the essential for now.
Recommended tags are something I want to implement after implementing changing ticket severity/tags. Ticket templates? Later. You could do much more with the tracker. I've suggested what I thought was the bare essential to make it usable.
Additionally, you'll need: 1. The ability to vote for bugs 2. The "email me when this bug is modified" checkbox (off by default) 3. The "Assigned To" field 4. Division in components(is it a bug in the parser or in the drawing code?) 5. Filters (show only Linux bugs, don't show Linux bugs, etc.) 6. Associate bug with URL(such as forum discussion, game that exposes the problem, etc.) 7. Submit files (test cases, patches, etc.)
THEN, it'll stand a chance to be a good tracker. But I believe my previous suggestions are more important.
1. I'm using Google's idea of starring, although I'm going to try and make it more visible 2. I haven't looked into how to email users 4. Probably will be part of suggested tags 5. Already planned 6. Won't implement 7. I haven't looked into how to upload files 1. I say this one because everybody hates "+1" posts.
Also, regarding "Feature Requests", you already have a feature request tracker, you just don't know it yet. If anything, a feature request type would make it easier to ignore them.
Also, auto-assign would be interesting. If different people are working on different parts of ENIGMA, then assigning a bug to those parts of ENIGMA would automatically assign it to the person that's working on it, who could then redirect it to someone else if he/she wanted to.
Set the severity to none. There's a reason why I don't explicitly name the tracker the "bugtracker". Auto-assign? You can remind me when spray's at a later stage of development.
|
|
« Last Edit: July 08, 2010, 08:43:48 pm by a2h »
|
Logged
|
|
|
|
|
notachair
|
|
Reply #23 Posted on: July 09, 2010, 05:04:37 am |
|
|
Definitely not a chair
Joined: Feb 2008
Posts: 299
|
Well, this is an old problem but...
I unchecked the "Allow users to email me" box, but they still can.
And it isn't a problem with the tracker. I've tried copying over some code from the default theme, see if it's fixed now. EDIT: I apologise to anyone who has previously gotten used to the "View New Posts" position, I've been thrown off as well
|
|
« Last Edit: July 09, 2010, 05:47:58 am by a2h »
|
Logged
|
|
|
|
|
|
|
MahFreenAmeh
|
|
Reply #27 Posted on: July 13, 2010, 03:03:32 pm |
|
|
sysadmin
"Web Team" Location: Austin, TX Joined: Apr 2008
Posts: 13
|
it's not named the bugtracker... but the underlying framework is named bugspray... hi.
|
|
|
Logged
|
sys(tem)admin(istrator) [java,c++,c,javascript,html,css,php,perl,ruby,python,sql] if you've got ideas, let me hear them.
|
|
|
|
MahFreenAmeh
|
|
Reply #29 Posted on: July 14, 2010, 03:12:47 pm |
|
|
sysadmin
"Web Team" Location: Austin, TX Joined: Apr 2008
Posts: 13
|
|
|
|
Logged
|
sys(tem)admin(istrator) [java,c++,c,javascript,html,css,php,perl,ruby,python,sql] if you've got ideas, let me hear them.
|
|
|
|