we need to simlify this bug tracking

This bug tracking is not working for me.  What it is doing is distributing the bugs out in zillions of tag rooms.  There is no central place to just go look for a bug. 

I propose a single tag for bugs.  

Then each bug is further classified as to what the functional part of the system the bug is in.  

We are too small for all the priority tracking.

We are almost at the phase where if a bug is not immediately fixed, it should be refered to via it's item in a project plan like What is next ?.  The fact that it is refered to in a plan, gives it a very practical priority. 

Also when the bug is fixed, then the bug tag will be removed and if there is no lasting value in the item otherwise, it would be nice for the author to delete it. 

I propose the tag ^bug

After a reasonable discussion period, I am going to do a global tag rename.

Discuss ...

Tags

  1. qa
  2. bug tracking

Comments


Mark de LA says
this is kinda where we started out! What you probably are looking for is an aggregator. In a sense the new search box allows you to type in the caret (^) and all those items get listed in the lefthand column. Being able to designate a bug anywhere and feedback it's severity & proposed priority is a fairly general treatment for bug tracking anywhere.

Mark de LA says
In general if you are looking for something to populate your project plan, then you search the s1....s9 first, then the p1....p8 & finally look for wishes in the w1...w9's . The other items being the functional part of the system, one would look thru them & see if there is a ^functional area tag on something you are working on. The procedure is really quite simple & the new search box is very helpful there.

Mark de LA says
If the priority & severity is too complex then that is an area to collapse & perhaps preserve just the severity numbers: ^s1...^s9 - note I rarely use anything deeper than severity 5.

Seth says
Mark, i want a single tag room that i can browse and see all the bugs and classify them or look for a bug in. We have no single tag room of bugs.

Mark de LA says
If you don't use some kind of severity, then you have to look thru all the bugs to figure it out for what is needed. In my experience beyond 75 bugs is hard to remember & track without some such scheme. When we release it to the public en masse, we are likely to find more bugs & complaints & requests for help files etc.

Seth says
The severity and the priority are not important bits of information to me. I know those things. Being the single developer one keeps a lot of the status in one's mind. But what i need to know is what bugs are out, i dont want to forget about a bug.

Seth says
Mark 2005-10-17 08:20:20 1540
If you don't use some kind of severity, then you have to look thru all the bugs to figure it out for what is needed. In my experience beyond 75 bugs is hard to remember & track without some such scheme. When we release it to the public en masse, we are likely to find more bugs & complaints & requests for help files etc.
If you want to keep the severity tags, that is fine.  I will probably ignore them.  But we do need a single tag room for all bugs.  The tag search does not do it, it just shows the tags, not the items.  When i look at bugs, i want to see the whole item.  An again what is a bug in those items should be clearly stated in the item, not the comments. 

Seth says
Also you are forgetting that the bug should be subclassified as to which functional part of the system it inhabits. So when i work on the rte i wouuld naturally visit s ^bug,rte. That is how things do not get lost. Then the tag room ^bug will show all of the functional parts of the system and perhaps how people have used different tags for the same function. This is very easy to go through and edit. Of course we need the feature that when you go to a tag room you just see the "related" tags in the list ... work in progress.

Seth says
Incidentally, as far as i can tell, from this bug tracking, there are just 14 officially reported bugs.

Mark de LA says
s ^rte works

Mark de LA says
If it has a caret in the name it classifies a bug - we agreed upon that sometime ago.

Mark de LA says
If tags can not work for this simple task, then tags are pretty much worthless for anything serious.

Seth says
Mark 2005-10-17 08:42:42 1540
s ^rte works
No it does not.  That shows everything about rte.  Not the bugs in rte.

Mark de LA says
I wonder if you can build a tagroom (aggregator) on a partial tag like the caret.

Seth says
Mark 2005-10-17 08:46:13 1540
If tags can not work for this simple task, then tags are pretty much worthless for anything serious.
Tags will work find for this task.  We have just systemattized it in a way that is not working for me.  

Mark de LA says
seth 2005-10-17 08:49:30 1540
Mark 2005-10-17 08:42:42 1540
s ^rte works
No it does not.  That shows everything about rte.  Not the bugs in rte.
Well as a total aggregator this does! It's just not i a room. If you like I can go thru the laborious job of building a spreadsheet (the traditional form). We started out with the idea of putting them all in a group like: group Test but then bugs got into the living stream from all kinds of places. Tagging was the last way to organize.

Mark de LA says
Sorry, the group link s/b uri http://fastblogit.com/Test%20and%20QA/

Mark de LA says
source:  No it does not.  That shows everything about rte.  Not the bugs in rte.
Well, I have adhered to the convention we agreed upon when I know something is a bug & that you agree or are likely to.  When I found a bug & could define the functional area I tagged it such that the functional area short description was preceeded by a caret.  Thus ^rte should have rte bugs and not everything rte

Mark de LA says
Notice what the search box picks up under rte.

Seth says
Mark 2005-10-17 09:07:31 1540
source:  No it does not.  That shows everything about rte.  Not the bugs in rte.
Well, I have adhered to the convention we agreed upon when I know something is a bug & that you agree or are likely to.  When I found a bug & could define the functional area I tagged it such that the functional area short description was preceeded by a caret.  Thus ^rte should have rte bugs and not everything rte
Ok, i see.  But then what if someone else spelled it differently.  so we might expect to find "^text edit".  If you put all the bugs together in one room, then the related tags should show up in a nice editable list.  We havent really gotten the "related tags" together so maybe you are not thinking of how easy it could work.

Mark de LA says
source: i see.  But then what if someone else spelled it differently.  so we might expect to find "^text edit".  If you put all the bugs together in one room, then the related tags should show up in a nice editable list.  We havent really gotten the "related tags" together so maybe you are not thinking of how easy it could work.
Welcome to the wonderful world of tags.

Mark de LA says
With data processing one would have a drop down list with all the allowed areas of the functionality pre-defined!

Seth says
Mark 2005-10-17 09:22:26 1540
With data processing one would have a drop down list with all the allowed areas of the functionality pre-defined!
Wait till we get lists of related tags going and  i think you will see your  drow  down lists start appearing.

Mark de LA says
You could still do that by providing a header for the tagroom with all the predefined tags in it & all we would have to do is copy the one closest to our idea of what the functional area is!

Seth says
Mark 2005-10-17 09:40:00 1540
You could still do that by providing a header for the tagroom with all the predefined tags in it & all we would have to do is copy the one closest to our idea of what the functional area is!
Actually the "related tags" list will do exactly that. 

See Also

  1. Thought RTE Matrix with 6 viewings related by tag "qa".
  2. Thought Proposed procedure with 0 viewings related by tag "qa".
  3. Thought [title (1611)] with 0 viewings related by tag "qa".
  4. Thought Triage with 0 viewings related by tag "qa".
  5. Thought need to agree on bug tags with 0 viewings related by tag "qa".
  6. Thought about: Wiki: Introduction To Fit with 0 viewings related by tag "qa".