Tree relationships & custom bug status groups with workflows
Posted: 03 Apr 2008, 10:25
Hello,
My company made some modifications to an older Mantis version, which we use for some time now. Since then, we were unable to upgrade because we would have to manualy apply those modification the new Mantis version.
We would like to move our upgrades to the main mantis source code so we would be able to upgrade out installation more often.
Here are the features we added:
1. Custom bug status groups and workflows selectable per project.
We define extra status groups with or without workflows in configuration file, then we can choose which status group we use for a project from the project edit page (create and update pages).
It may also be done manualy from manage configuration UI screen.
2. Tree model relationships
We used the existing relationship graph model to implement a tree model. We did it by limiting the number of "child of" relations in a bug to one and by detecting circular relations.
That way, if we have a larger bug/task, we can divide it into smaller tasks and assign to different people.
There is also a new column for displaying hierarchy path in bug list view.
To mantain compatibility with older projects, tree relationships must be explicitly enabled in project edit page (create or update pages) or through configuration.
What is the procedure in pushig contributed code to mantis ? Should I send a patch to mantis dev mailing list ?
What are the chances they will apply this patch ? The code doesn't add any files and doesn't break any existing features.
My company made some modifications to an older Mantis version, which we use for some time now. Since then, we were unable to upgrade because we would have to manualy apply those modification the new Mantis version.
We would like to move our upgrades to the main mantis source code so we would be able to upgrade out installation more often.
Here are the features we added:
1. Custom bug status groups and workflows selectable per project.
We define extra status groups with or without workflows in configuration file, then we can choose which status group we use for a project from the project edit page (create and update pages).
It may also be done manualy from manage configuration UI screen.
2. Tree model relationships
We used the existing relationship graph model to implement a tree model. We did it by limiting the number of "child of" relations in a bug to one and by detecting circular relations.
That way, if we have a larger bug/task, we can divide it into smaller tasks and assign to different people.
There is also a new column for displaying hierarchy path in bug list view.
To mantain compatibility with older projects, tree relationships must be explicitly enabled in project edit page (create or update pages) or through configuration.
What is the procedure in pushig contributed code to mantis ? Should I send a patch to mantis dev mailing list ?
What are the chances they will apply this patch ? The code doesn't add any files and doesn't break any existing features.