On Nov 4, 2006, at 13:35, Victor Boctor wrote:
> On 11/4/06, Ryan Schmidt wrote:
>> Does anybody have an opinion one way or another with regard to the
>> below? I receive an email for each newly reported issue in Mantis,
>> and it's nothing other than spam when half of them are not in fact
>> issues with Mantis. \r
>> On Oct 28, 2006, at 18:08, Ryan Schmidt wrote:
>>> I'm getting tired of dealing with all the bogus reports in the
>>> official issue tracker. People are constantly using the main issue
>>> tracker when they should be using the demo issue tracker or some
>>> other project's issue tracker. This wastes our time.
>>> Can we please add a message in big bright red letters to the top of
>>> the issue report page on the official tracker advising people in no
>>> uncertain terms that this is not a demo, and providing them with a
>>> URL to the demo right there? Something like this:
>>> ATTENTION: THIS IS NOT A DEMO. THIS IS THE REAL ISSUE TRACKER FOR
>>> TRACKING REAL ISSUES IN THE MANTIS PROJECT. IF YOU ARE TRYING TO
>>> REPORT AN ISSUE IN A DIFFERENT PROJECT, YOU ARE IN THE WRONG PLACE.
>>> IF YOU ARE TRYING TO EVALUATE MANTIS, PLEASE USE THE <a
>>> http://www.futureware.biz/mantisdemo/">DEMO</a> INSTEAD.
>>> BEFORE SUBMITTING A NEW ISSUE, PLEASE <a
>>> href="view_all_bug_page.php">SEARCH</a> THE EXISTING ISSUES; YOUR
>>> ISSUE MAY ALREADY HAVE BEEN REPORTED. PLEASE DO NOT SUBMIT DUPLICATE
> I haven't notice that it is that bad. I think such issues have been
> reduced since the link to the demo site was included in the main
> website side menu. I wonder if other developers have the same issue.
> If we are to add a statement. I would add a very brief one line
> statement that links to the demo website.
> My preference is to keep things as is. However, I am open for
I consider the situation pretty aggravating currently. If we were
getting maybe 1 or 2 false reports each month, I might leave it as it
is. But just in the past week, we have received the following bogus
> Date: November 6, 2006 19:03:09 CST
> Subject: [mantisbt 0007567]: Upload Photos
> Date: November 6, 2006 18:10:09 CST
> Subject: [mantisbt 0007566]: Upload Jokes
> Date: November 6, 2006 15:59:07 CST
> Subject: [mantisbt 0007565]: what the F### is wrong with this thing?
> Date: November 6, 2006 15:18:14 CST
> Subject: [mantisbt 0007564]: Upload NEW PARLIAMENTARIANS
> Date: November 4, 2006 10:02:06 CST
> Subject: [mantisbt 0007560]: Changing the present ELECTIONS WEBSITE
> into a BUSINESS WEBSITE
> Date: November 2, 2006 14:46:06 CST
> Subject: [mantisbt 0007554]: bla bla
> Date: November 2, 2006 14:26:10 CST
> Subject: [mantisbt 0007553]: The text apears in english ojn
> Japanese site
> Date: October 31, 2006 08:39:07 CST
> Subject: [mantisbt 0007550]: This is a test problem submitted by me
It is not an effective use of developer time to look at all these
nonsense reports and deal with them. It should be the users who are
so inconsiderately using the production bug tracker for their own
testing, or who do not realize that they are in the wrong tracker,
who should be asked to spend a little extra time to use the correct
The second paragraph of my proposed message above is of course aimed
not at people testing Mantis but at people reporting duplicate
issues. This is also a problem, but perhaps a less-severe one. I
would agree to leaving out that part of the message to start with.
But I remain in favor of the notice being in huge red letters that
nobody, and I mean nobody, will be able to avoid reading. Take this
as an example:
Yes, it looks ugly, but the point is not to look pretty; the point is
to look glaring and attract attention so that everybody will read it
and obey it.