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.
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.