Request: Could we have a Logos Bug Tracker?
Comments
-
Bradley Grainger said:
Any new field can be added with the [[field name::data]] syntax in the wiki page. (Or {{?set field name::value}} if you don't want it to be visible.) Then add "|?field name" to the query at http://wiki.logos.com/Logos_4_Bugs to display that field. Once the page is displayed, the field headers can be clicked to re-sort (but the wiki engine doesn't currently support automatically sorting by anything other than title or last revision date.)
You can also run ad-hoc queries, e.g., by entering "status:pending" into the wiki search box at the top left to find all pending bugs: http://wiki.logos.com/search.aspx?q=status:pending
0 -
Dave Hooton said:
I've stumbled around the wiki bug recorder and come up with some suggestions:
1. I don't think everybody should be allowed to add a bug report because there will be many spurious reports that somebody will have to monitor and possibly remove.
2. Not everybody should be expected to do so, either. Many users just want to report a problem or difficulty without caring that it is a bug, then having to decide if it already exists, etc.
3. So the power users should be the ones to create bug reports from the forum + their own; which means the first one handling a post should report it under their name (not the actual user!) and encourage the posting of any logs or images and make a statement to the effect that it has been reported on the wiki. That way everyone is informed (OK, I put up a report in Todd's name, but I knew he'd get around to it
).
Dave,
If a Power User is to be able to put up a bug report, they need certain info. Is it easier to have the original poster do that reporting or for us to have to ask, version, hardware, step by step process?
I didn't find the Bug Report easy to manage the one report I've made, so maybe we need to work out a template that posters can follow in the forum and then we can use that to put on the wiki.
I realize this is confused, but that reflects my state of mind this morning.
Chris
0 -
Chris Elford said:
If a Power User is to be able to put up a bug report, they need certain info. Is it easier to have the original poster do that reporting or for us to have to ask, version, hardware, step by step process?
I didn't find the Bug Report easy to manage the one report I've made, so maybe we need to work out a template that posters can follow in the forum and then we can use that to put on the wiki.
My thinking is that we get the poster to to clarify the issue and supply needed information (image/log report) as we have already been doing, then we can create the bug report. Believe me, it will be more involved all round to get the average user to fill in a template with which they are not familiar (and they usually have no desire to get involved with a process). It took a little "stumbling around" for me to create my first report!
Dave
===Windows 11 & Android 13
0 -
Dave Hooton said:Chris Elford said:
If a Power User is to be able to put up a bug report, they need certain info. Is it easier to have the original poster do that reporting or for us to have to ask, version, hardware, step by step process?
I didn't find the Bug Report easy to manage the one report I've made, so maybe we need to work out a template that posters can follow in the forum and then we can use that to put on the wiki.
My thinking is that we get the poster to to clarify the issue and supply needed information (image/log report) as we have already been doing, then we can create the bug report. Believe me, it will be more involved all round to get the average user to fill in a template with which they are not familiar (and they usually have no desire to get involved with a process). It took a little "stumbling around" for me to create my first report!
Okay, I'm with you on this. To get the bug reports and beyond!
0 -
In http://community.logos.com/forums/t/6846.aspx Mark reports that a bug still exists that is listed as fixed in B4. In the Bug List it is marked as fixed. How do we go about re-reporting this as not fixed?
Chris
0 -
The advantage of posting to a public forum rather than emailing Logos directly is that someone may reply that you are simply doing something wrong with the software. Sometimes what appears to be a bug is really just an aspect of the program that is not clear and thus the user uses it incorrectly. I like the idea of a central area to report bugs and an opportunity for people to respond.
0 -
Chris Elford said:
In http://community.logos.com/forums/t/6846.aspx Mark reports that a bug still exists that is listed as fixed in B4. In the Bug List it is marked as fixed. How do we go about re-reporting this as not fixed?
Chris
Steve's new bug report references the old one - a very clean way as the history is preserved.
Dave
===Windows 11 & Android 13
0 -
Harry Hahne said:
The advantage of posting to a public forum rather than emailing Logos directly is that someone may reply that you are simply doing something wrong with the software. Sometimes what appears to be a bug is really just an aspect of the program that is not clear and thus the user uses it incorrectly. I like the idea of a central area to report bugs and an opportunity for people to respond.
Harry,
These forums are the place to report a Bug, but we are also putting them into a page on the wiki to centralize, organize and track them. People can edit them there and see what is happening to them.
Chris
0 -
Dave Hooton said:Chris Elford said:
In http://community.logos.com/forums/t/6846.aspx Mark reports that a bug still exists that is listed as fixed in B4. In the Bug List it is marked as fixed. How do we go about re-reporting this as not fixed?
Chris
Steve's new bug report references the old one - a very clean way as the history is preserved.
Agreed. That's what I was trying to envision. You guys are way ahead of me.
Chris
0