Bug 100832
| Summary: | unable to find bugs I've opened -- bug searching nearly useless | ||
|---|---|---|---|
| Product: | Documentation | Reporter: | Jo Rhett <jrhett> |
| Component: | Books & Articles | Assignee: | Gabor Kovesdan <gabor> |
| Status: | Closed FIXED | ||
| Severity: | Affects Only Me | ||
| Priority: | Normal | ||
| Version: | Latest | ||
| Hardware: | Any | ||
| OS: | Any | ||
|
Description
Jo Rhett
2006-07-25 21:50:13 UTC
State Changed From-To: open->feedback If I search for bugs with originator Rhett, I get 11 lines in listing. Note that GNATS (software used for a bug tracker) does not search email addresses, just names. For searching in closed bugs, just tick Closed reports too checkbox. Clear now? :) Responsible Changed From-To: freebsd-www->pav Deal with this Why is there a "State" pulldown with Open/Closed and a checkbox as well. I checked the former, but overlooked the latter. Duplication of the field can't possibly be useful. And yes -- I understand that it doesn't search e-mail fields. That's why its a bug. Searching based on last name is useless. Do you know the proper spelling for the last names of all the people you chat with on a regular basis? No... How about their three-letter e-mail address? Yes. See? -- Jo Rhett senior geek Silicon Valley Colocation > Why is there a "State" pulldown with Open/Closed and a checkbox as > well. I checked the former, but overlooked the latter. Duplication > of the field can't possibly be useful. So you can search all states but closed. How would you do that with just the pulldown? > And yes -- I understand that it doesn't search e-mail fields. That's > why its a bug. Searching based on last name is useless. Do you know > the proper spelling for the last names of all the people you chat > with on a regular basis? No... How about their three-letter e-mail > address? Yes. See? Well, I remember their names but not their email addresses. But whatever. GNATS is a third-party software. I just don't see a chance for us to do some local bending of it. -- Pav Lucistnik <pav@oook.cz> <pav@FreeBSD.org> See file. Click file. Get file. On Jul 25, 2006, at 3:06 PM, Pav Lucistnik wrote: >> Why is there a "State" pulldown with Open/Closed and a checkbox as >> well. I checked the former, but overlooked the latter. Duplication >> of the field can't possibly be useful. > > So you can search all states but closed. How would you do that with > just > the pulldown? Choose "Closed" in the State pulldown? Seems simple to me. And "Any" in the State pulldown clearly is not Any -- it's "Any except for Closed" And seriously, how should I find closed bug reports? Do I have to choose "Closed" and ALSO click the checkbox? This makes no sense. It's far beyond counter-intuitive. Intuitive might be a state list that doesn't include Closed and put the checkbox right beside it, where the eye is already focused. If the checkbox is really necessary, which I just don't see. >> And yes -- I understand that it doesn't search e-mail fields. >> That's >> why its a bug. Searching based on last name is useless. Do you >> know >> the proper spelling for the last names of all the people you chat >> with on a regular basis? No... How about their three-letter e-mail >> address? Yes. See? > > Well, I remember their names but not their email addresses. But > whatever. > > GNATS is a third-party software. I just don't see a chance for us > to do > some local bending of it. I guess the answer is for me to file a bug report with them. But seriously, doesn't someone "own" the bug database? If so, they are probably already familiar with the GNATs bug system/process and how to get things reported and/or fixed... -- Jo Rhett senior geek Silicon Valley Colocation > >> Why is there a "State" pulldown with Open/Closed and a checkbox as > >> well. I checked the former, but overlooked the latter. Duplication > >> of the field can't possibly be useful. > > > > So you can search all states but closed. How would you do that with > > just > > the pulldown? > > Choose "Closed" in the State pulldown? Seems simple to me. > > And "Any" in the State pulldown clearly is not Any -- it's "Any > except for Closed" > > And seriously, how should I find closed bug reports? Do I have to > choose "Closed" and ALSO click the checkbox? This makes no sense. > It's far beyond counter-intuitive. > > Intuitive might be a state list that doesn't include Closed and put > the checkbox right beside it, where the eye is already focused. If > the checkbox is really necessary, which I just don't see. > > GNATS is a third-party software. I just don't see a chance for us > > to do > > some local bending of it. > > I guess the answer is for me to file a bug report with them. But > seriously, doesn't someone "own" the bug database? If so, they are > probably already familiar with the GNATs bug system/process and how > to get things reported and/or fixed... Well, if you're only after changing the query-pr-summary.cgi web form, then we can work on that. Changing the search logic with respect to originator field would require changes to vendor code. Note that we're running really ancient version of GNATS, so reporting to the vendor might not be all that useful. -- Pav Lucistnik <pav@oook.cz> <pav@FreeBSD.org> "Ragtime" contained about forty-five seconds of Elizabeth McGovern completely topless, but it got a "PG" in 1980. I have no idea why that did, or "Titanic" got PG-13, yet "Merchant of Venice" gets tagged with an "R". The MPAA is an intellectual and aesthetic embarassment. -- comment from IMDb board on US movie rating system State Changed From-To: feedback->open Some feedback obtained Responsible Changed From-To: pav->freebsd-www Assign back to the pool. On Jul 26, 2006, at 12:56 AM, Pav Lucistnik wrote:
> Changing the search logic with respect to originator field would
> require
> changes to vendor code. Note that we're running really ancient version
> of GNATS, so reporting to the vendor might not be all that useful.
Are these things fixed in newer versions? If so, then why not just
change the bug to "please upgrade GNATS" ?
--
Jo Rhett
senior geek
Silicon Valley Colocation
> > Changing the search logic with respect to originator field would > > require > > changes to vendor code. Note that we're running really ancient version > > of GNATS, so reporting to the vendor might not be all that useful. > > Are these things fixed in newer versions? If so, then why not just > change the bug to "please upgrade GNATS" ? My understanding of GNATS upgrade issues is that no one from the group of people who have the rights to do this, have time or will to do this. -- Pav Lucistnik <pav@oook.cz> <pav@FreeBSD.org> And the sign said long haired, freaky people need not apply. State Changed From-To: open->closed Hi Jo, I understand your concerns about it, but as Pav said, the search engine belongs to GNATS not our script, so we cannot do much about this. As for the states, I think the current behhaviour is practical. An interested party usually looks for PRs that are not closed, but still should be solved. When I look for something to work on, I also need to dig amongst non-closed reports, so i think it suffices the most needs. Committers can search via the query-pr command line interface and grep in PRs. But you don't have to be a committer to do so, you can mirror the GNATS database if you want to run a more advanced search, you can decide if it's worth to you. Check /usr/share/examples/cvsup/gnats-supfile if you want to fetch the PR database. Unfortunately, I cannot offer a simpler solution for you, so I'm closing this PR now, since it is open for a long time, but did not get us any step forward. If you have any comments or suggestions, please feel free to reply. Regards, Gabor Responsible Changed From-To: freebsd-www->gabor Track. |
