Mantis Bug Tracker - Forums

Currently I'm developing a tool for describing development processes (http://automotive-scrum.org/demo.html).
The tool is getting in an alpha test phase and I'm looking for examples, I can describe with the tool.

One chapter shall be: "using Mantis as a bug tracker"
Also I already worked with Mantis a few years ago, I'm far from being a Mantis expert.

So I'm looking for some help on this issue.

My hope is, that I can find someone here in the forum, who can proofread my description?

I personally can only add information from the different Mantis descriptions on the internet and my personal experience (which is not much).
If it shall become a good description, I need to have an expert as co author

I can't promise anything, but a bit of review should be possible.
As you and me are Germans (at least according your Impressum page) it would be easier for me to write comments in German.

Thanks a lot for that offer. I expect a little bit of a description after weekend. And yes, comments in German language are welcome.
I let you know, when I've something to review.

I finished a first draft version of the description. There is still some text missing, but it would be great, if you could review the state chart on:

http://automotive-scrum.org/minimalMant ... issue.html

All transitions in the state chart are linked, so you can navigate to a description of each of the activities (where the text must be extended).
There you can also see the attached roles.
At this state it's mainly important for me, if I designed the state chart in a correct way and described the usage of the states correct.

Are you aware that
a) Mantis status values can be customized (remove existing /add own values) https://www.mantisbt.org/docs/master-1. ... IZE.STATUS
b) The workflows can be customized https://www.mantisbt.org/docs/master-1. ... IZE.STATUS

You can use Mantis in quite different ways, e.g. there are installations having just "New", "Assigned" and "Closed" for status, installations that added status "In Process" that follows status "Assigned", installations where just users of role "Manager" are allowed to set status to "Closed", ...

I am not sure if I understand what's your goal with this.
Do you want to describe how Mantis works out of the box without any customization?
By default, there is no workflow defined, which means that all states are accessible from any other, by anyone.

astade wrote:described the usage of the states correct.

There is a description of the default status values at https://www.mantisbt.org/docs/master-1. ... CLE.STATUS

atrol wrote: By default, there is no workflow defined, ...

That's exactly my intension.

For every aspect of software development it's the same. You have "tools" on the one hand and the problem of defining a "workflow" on the other hand.
Depending of how big and how experienced your team is and how "formally" you are obliged to work (e.g. automotive) the defining of the workflow is a central issue. Mostly you have a slightly different workflow deffinition in every team members head.

atrol wrote: Are you aware that
a) Mantis status values can be customized (remove existing /add own values) https://www.mantisbt.org/docs/master-1. ... IZE.STATUS
b) The workflows can be customized https://www.mantisbt.org/docs/master-1. ... IZE.STATUS

I'm almost aware. But before you can start customizing, you have to make up your mind, what shall be the workflow you want to customize.
You have to write down your target workflow.

So I developed a tool for defining workflows.
My target was:" How can you define and write down workflows, that they are complete, consistent and easy to understand."

After the tool is almost feature complete now I want to define some workflows (e.g. as a test for the tool).

For whatever reason, I decided to describe "issue tracking with Mantis" as one of my first workflows. And here the focus is not the "you can do, what you want" approach, but finding out, what I want

atrol wrote: Do you want to describe how Mantis works out of the box without any customization?

I don't want to describe Mantis at all (this is already done elsewhere). I want to describe a workflow and show how Mantis can support the workflow.