Mantis Bug Tracker - Forums

Have a look at JIRA http://www.atlassian.com/software/jira/ ... troduction for some alternative ideas on bugtracking.

Then "you" personally should not be a member of the project. But surely "being" the admin user is like to "being" root under Unix systems - you should not use it as your workday login, but only when performing some task that requires the privilege, such as creating a pr...

Sorry, yes, you're right - the Update does as you say.

I was mistakenly assuming that Update would trigger an 'update' with form data on that page, rather than changing to an 'Update' page.

RTFM ? But adding tooltip help would assist when wording on a button was not sufficiently explicit ...

Thx.

Someone has entered a very brief and uninformative Summary.
It's important that useful text appears in the top-level listing.

As Admin, how can I 'correct' this field ? (short of editing via MySQL ...)

Is there a 'clean' writeup about adding a new issue status ? I have tried the approach in the manual.mantisbt page, but since there is conflicting/incomplete advice, it's not clear exactly what has to be done. This page should be scrapped and rewritten correctly - an uncorrected manual page should n...

I use Categories to divide the Issues into broad areas, e.g. with our application: Installation, Database, Graphics, Other. This gives the appropriate specialist the chance to spot issues of particular relevance. Perhaps for your web application the categories might be: Installation, Configuration, ...

Since Mantis works from the database, you should look at the MySQL documentation about syncing two databases.

The problem I can see is what happens if a new Issue is created in each Mantis by different people - they will have the same Issue number but be different in content.

Is the intended usage of the different categories of Severity recorded anywhere ?

For example, how does 'tweak' differ from 'trivial' ?

I wanted to set these distinctions out for our users so that they would be used consistently, and therefore useful when looking at a report.

Could I ask that the Subject title be a useful phrase rather than just a number ?

Even something like "release date 0.19.3 ?" would be good !

Thx

"F* script kiddies... " - it's not good English to use those words (despite being common in American movies !!) When I worked in Belgium, I asked my collegues not to use such English words, but to use the Nederlands equivalent - they said, "No, it's too bad a word to use !" - I r...

For new projects, it would be helpful if all the custom fields and categories could be copied from an existing project at the same time as the project is created (or failing that, in Manage Project - projname). e.g. Copy custom values from [xxxxxxv] Project Name This would help to avoid mistakes as ...

One filter I was looking for but didn't find was 'any issue I had changed'. In other words, any issue that I had reported, updated or touched in any way. I see this as another filter type which has a User dropdown, with a panel of checkboxes saying reported[] updated[] etc. I have added this as a No...

That sounds good - definitely the way to go. I hope that the email permission setting (including domain filtering) is moved to the DB too, see my recent Note in http://bugs.mantisbt.org/view.php?id=2609 With all those settings in global variables, it takes me back to some old Basic programs I had to...

Thanks for that. No doubt one day all these $g_ 'tweaks' will be exposed on an Administrator's 'Manage Configuration' page. How about a section in the Manual e.g. 'How to set up Workflow' ? The thinking behind this and other features could be described, to allow more use to be made of them. Currentl...

Has anyone done a mod to ensure that an issue can only be closed by (e.g.) a Manager ? I have inserted the mods from the manual page to implement rudimentary workflow, and would like to have a restriction that meant that an issue could not be closed by just anyone. This is to enforce a signoff proce...