Summary per 'Fixed In Release', or better filter on it.

General discussion of Mantis.

Moderators: Developer, Contributor

Post Reply
mgerben
Posts: 11
Joined: Feb 15, 2005 2:42 am
Location: Netherlands
Contact:

Summary per 'Fixed In Release', or better filter on it.

Post by mgerben »

I would very much like to see the Summary expanded to include an overview of bugs new/solved/resolved/still_open per version number; much like it's done per developer at the moment.

This would help a lot to see how many - and most importantly which - bugs are still to be solved before a particular release is ready.

It also helps to see for which bugs no release has been set yet;
This is an important one for me: My team filters the bugs on the overview page per release. If someone forgets to fill the 'solved in release' field the bug might not end up in the overviews and might end up forgotten.
This can happen: The field is not mandatory and not everybody working on the bug knows the release-planning and knows which bug is to be solved in which release.


In addition to this, it's not possible to filter on 'fixed in release' = NONE.
That would already help a lot.

I made an issue about this: number 5232.

Thoughts?

thraxisp
Developer
Posts: 509
Joined: Feb 13, 2005 10:38 pm
Location: Ottawa, Canada
Contact:

Filter on Fixed-in Version

Post by thraxisp »

The ability to filter on blank fields ([none]) is in CVS and should be available in the next release.

mgerben
Posts: 11
Joined: Feb 15, 2005 2:42 am
Location: Netherlands
Contact:

I changed the changelog

Post by mgerben »

I really needed this.

Our people filter on 'fixed in project' to see what work still has to be done.
But when a bug is entered, it has no 'fixed in project' and if you forget to set one, the bug will never show up once you filter.

So I adapted the changelog. I copied it to a new file which I called 'releaseplanning'.

It does three things:

- It shows all bugs, not just the ones with status FIXED.
- It displays the status of all the bugs as well
- It lists all bugs that are not assigned to a version/release yet.

It looks like this:

Version 3
======
[348] [ASSIGNED] - description, blablabla
[346] [FEEDBACK] - description, blablabla
[344] [NEW] - description, blablabla

Version 2
======
[318] [ASSIGNED] - description, blablabla
[337] [FIXED] - description, blablabla
[326] [FIXED] - description, blablabla
[314] [FIXED] - description, blablabla

Version 1
======
[312] [FIXED] - description, blablabla
[361] [FIXED] - description, blablabla
[311] [FIXED] - description, blablabla
[301] [FIXED] - description, blablabla

Known bugs not assigned to version yet
=========================
[456] [NEW] - description, blablabla
[428] [FEEDBACK] - description, blablabla
[413] [FEEDBACK] - description, blablabla


From this list you can deduce we're working at version 2, and all but one bugs are fixed.
Some work is already done on version 3.
All bugs for version 1 have been fixed.
There are also 3 new bugs for which we don't know in which version they're going to be fixed (456, 428 and 413).


If people are interested, how do I submit this code, considering I don't have a CVS account?

Post Reply