Mantis Logo
Mantis Manual
Manual
Appendix

ChangeLog
Credits
Alternatives
Links
Security
Manual Improvements
Testmonials


Partner Links


Manual Improvements
Last Modified: September 3, 2003 18:09PM
(Any)
Description

The aim of this page is to allow Mantis Manual readers to contribute notes for suggesting manual improvements. Possible improvements include:

  • General comments
  • Missing topics
  • Manual layout
  • Manual look'n'feel

This page should not include the following:
  • Improvements to Mantis itself. This should be added to the bug tracker at http://mantis.calaquendi.net.
  • Topic specific comments which should be added to the topic pages.

User Contributed Notes
Manual Improvements
Add Notes About Notes
svast[AT]NOSPAMmeetingone.com
03-Mar-2004 5:21
#79
Localizing this user manual would be great.

I am thinking about the way to help the project by translating it into French (my native language), and providing that to the community.

Any clue or schedule about that?
heiko1.schneider@volkswagen.de
08-Mar-2004 3:04
#82
Is it possible to get the manual as a download? (maybe .html/.chm/.pdf/...)

I need it, because most of our users do not have access to the www. They are allowed to access the Intranet only.
kenrus@mindspring.com
26-Jul-2004 9:42
#178
Testmonials should be spelled Testimonials

http://manual.mantisbt.org/manual.appendix.testmonials.php
bvanderwerf@NOSPAMcrownintl.com
17-Aug-2004 10:50
#186
It would be great if the manual was written from a functional viewpoint instead of a page-centric viewpoint.

In other words, I want topics on how do I setup a project, how do I report and view bugs, how do I get reports, how can I control e-mail, etc.

Also, as has been mentioned, a downloadable PDF version of the manual would be awesonme!

Thanks...
darkcryst@gmail.com
23-Nov-2004 6:24
#268
Actually covering the software fully would help ;)

Many functions of the software are completly shrouded in mystery.. as there is no documentation for them.
noemail@nospam-ugh.com
17-Feb-2005 11:47
#358
What does it mean to have a protected user?
hairmare-mantisbt@purplehaze.ch
14-Apr-2005 6:49
#409
Some translation info on the manual would be nice. Where to go, who to ask, into what language to translate.
I would be spending some time with the german version...

Lucas
simon_at_gramjuhl_dk
10-May-2005 3:27
#433
I would be nice with a e.g. one page or PDF version for easy printing.
jn@it.swin.edu.au
08-Aug-2005 0:44
#560
These notes do not properly recognise URLs whith ~ and & characters in them.

There should be a standard way of obfuscating email addresses.

The optional email address is acutally required, and if you click back, the note text gets forgotten.
Si Brindley
16-Aug-2005 7:04
#565
"Change Log" in the Manual contents (Under Appendix) should link to the live Change Log (as in the main site menu), as it is out of date.
blesstiti@yahoo.com
20-Sep-2005 21:16
#619
Questions on 'Summary' page
1. What is the calculation for 'Reporter Effectiveness' section?
2. I posted a new one and only bug for a project today, however under the 'By Date (days)' section, all the days will show '1'. Why?

Couldn't find in the manual

Thanks for answering :)
jamesvl at trinitylight dot com
23-Nov-2005 12:10
#727
If this manual were a wiki I would have made several small improvements already (and I'm just reading through it after my initial install for the first time).

As a first-time reader I have questions like "What are some good Project categories for a project of type ____?" that the manual doesn't cover at all, and reading people's comments is a pain (especially when the same comment is submitted about five times).

But since it's not a wiki I have no idea how to actually make changes or how comments in this section are used. Oh well...
mNOSPAMfisher@SNOSPAM.regenstriefNOSPAM.org
15-Aug-2006 6:48
#1229
My Account -> Preferences should be documented.
dan
12-Nov-2006 8:33
#1290
I cannot find a topic on how to submit a new bug report.

I was looking for a topic on how to submit a report via email, and found there isn't even a how to submit via mantis itself.

Dan
ross@biostat.ucsf.remove.edu
05-Dec-2006 21:01
#1314
The manual dives right into configuration without explaining the system that is being configured, or even its normal use. As far as I can tell, that explanation never comes.

I think it would be useful to begin with a discussion of the concepts of the system and the expected flow of handling a bug. I did eventually find a discussion of at least what some of the statuses meant on one of the page descriptions.

I also think it would be more natural to put regular use next, and then administration. I also agree with the earlier comment favoring a functional approach to the manual: describe how to do tasks, rather than screens and menus.

Examples of conceptual background:

What statuses can a bug have?
What kind of people does the system recognize (e.g., anonymous, user, developer, administrator...) and what are their rights?
What do the severities mean?
What is the model for relations between bugs?
What are the usual sequence of changes in the state of a bug? What are the unusual but permitted sequences, and when might they be appropriate?
sptubby@hotmail.com
18-Jan-2007 1:53
#1356
View Issues Screen

All the filters are self explanatory except following

Change(hrs) - I read somewhere on a forum that this does not filter but impacts what issues are highlighted in the list in bold? Assume it applied to the "updated" field and one enters a number of hours so one can see all issues updated in the previous "x" hours

Date filter - I think that this reltaes to the creation date fo the issue rather than the last updated date. It would help if this were made clear in the manul
Add Notes About Notes
Last updated: Wed, 20 Aug 2008 - 10:20:50

Mantis @ SourceForge