|
|
a integrated pn system (and maybe forum) would also be nice but is not necessery because they can mail each other if the want to talk about the bugs and the solutions... |
|
|
|
Integration with svn is already possible as far as I know (not tested it yet myself). I thin there was a post in victor's blog about this; see e.g. http://www.mantisbt.org/forums/viewtopic.php?f=4&t=4330&p=11083. What else would you need? |
|
|
|
BTW: dup of 0000959? ;-) |
|
|
|
integrated todo-list system would be nice...
if you release a beta and you have not implemented "half" of the program...
you have a dev-team intern todo list...
is there any way to do this in mantis?
if not this is a requested feature... |
|
|
|
Hmm to do list?
Seems I have implemented something like ordered todo/task list in mantis.
And it isnt a minor change. Now im about to beta test it so if anyone is interested let me know. |
|
|
|
@smig1o, I am interested to know more about what you have implemented.
@DevilHUnter - I am interested to know why your need is not covered by the Roadmap feature. |
|
smig1o
2008-02-17 05:38
reporter
~0017090
Last edited: 2008-02-17 10:25
|
So prepare for a longer story ;)
<head>
I work for Systherm-info. We develope some software and we use mantis as our bug tracking system.
</head>
<body>
About 6 months after I've implemented mantis into sytherm it turned out that there is a gap between >ASSIGNED< and >RESOLVED< status. My boss didn't know what bug im currently working on. So I have decided to put another status named >PROCESSED< to inform everybody what I'm currently doing. That >PROCESSED< status is important in my task list idea.
After that I've tried to put my boss task list into the mantis. But we meet one problem. There was no way to keep tasks in desired order. Of course there is priority but you can set same priority to many issues and this will make disorder in ordered list. Another problem is fact that my boss is only responsible for assigning tasks to developers but he isnt deciding which task should be done first. So now he must go to "task manager" (a man that contact with our customers and knows what do they need) and discuss what to do first and its time consuming process.
Then he puts it on project task list in desired order. This order is changed from time to time. This list is kept in separate Word document cos its easy to reorder it. He has, also, another Word document where he assign task to developers. That means 3 sources of knowledge about what developer should do next (mantis for bugs, and 2 tasks list for unassigned and assigned tasks).
So, since Mantis API seems to be quite easy I've decided to implement ordered task list in it.
<PROJECT REQUIREMENTS>
- task list must keep its order
- there must be separate unassigned (sent to developer) and unconfirmed (should we work on it?) list for each project
- each user should be able to see his own task list in correct order
- there must be a user named task manager that will set the order of task. He may or may not be a project manager
- some tasks have deadline which should be highlighted
</REQUIREMENTS>
<DATABASE CHANGES>
I have added 2 columns into mantis_bug_table:
- task_order smallint default 0
- deadline date default null
</DATABASE CHANGES>
<WORKFLOW>
Any issue with severity > FEATURE is considered as bug and is processed in classic >mantis way<.
Any issue with severity == FEATURE is considered as task and is put to project unassigned task list. As long as it its status == NEW reporter can close the issue or change its severity. Only project manager or task manager can appprove task to farther process. When task status is > NEW reporter cannot close/delete it.
Task manager should sort unassigned task so project manager could assign them to correct developer. Only task manager or project manager can close unassigned task. Task manager cannot assign task to developer.
Tasks are shown on separate list. As long as they status < PROCESSED they wont appear on issue list. When developer starts working on the task he should switch its status to PROCESSED. Since then it appears on issue list so anyone who browse issues list can see what tasks/issues are currently >under construcion< :).
Is task has deadline set it will appear on tasks list and on view issue page. It status < RESOLVED date background will be red so no one can miss it ;)
Status >= RESOLVED will put its background back to normal.
Everything going into issue history too.
</WORKFLOW>
<BROWSER REQUIREMENTS>
I use javascript to reorder tasks so it must be turned on to see its working.
</REQUIREMENTS>
<TO BE DONE>
- I need to add email notifications to this new status.
- Everything should be tested
- Tasks re-ordering process can be broken because I didnt find a way to use transactions during reorder. If 2 person will try to reorder bugs in the same time the order may be a bit differrent than they expected.
</TO BE DONE>
This is first and the only task list project description so it may be a bit confusing. If so. let me know.
Oh, almost forgot. English isnt my native language...
</BODY>
I'll post 2 screenshots..
|
|
|
|
it is not a feature it is simply not implemented yet....
and it should be able to hide this "category" - visible only for dev-team...
do not know if this is already possible in mantis...
if it is i do not know how... |
|
|
|
Seems I'm ready to release a patch.. Any beta testers around?? |
|
|
|
I'm up :) |
|
|
|
Ok here we go.
Patch is made against Mantis v. 1.1.1. Be sure usage of javascript is turned on.
I'm sure you know how to apply it. Im not sure if icon files are in patch file but its not a big problem.
I have added new status: PROCESSED and new user level: TASK_MANAGER. So I had to change config_defaults.inc.php:
$g_status_enum_string and $g_acess_level_enum_string.
I put some configuration options at the end of this file.
NOTE! $g_task_enabled is in the file but its not used atm.
I put custom_strings_english.inc.txt in ./lang subdir. This file contains all new strings needed by task list. It should be merged with original strings_english.txt.
./admin/upgrades/update_tasks contains all several sql queries that upgrades database.
After that new menu >Task< item should appear and all issues with >FEATURE< severity should go there.
Of course dont try to do it on production server. Patch need to be tested.
Good luck. :)
Oh, btw. pszmigielski (at) systherm-info (tiny dot) pl <- I check this mail often. |
|
