Cheers for that Victor, I'll put that method to the team.
A wee bit of background information, our company has been using Mantis since
2003 and it's usage is frequently and daily (DB is 8GB). Only since I have
taken over running it we have really pushed for changes, more functionality,
different use of fields etc. We are currently in the process or redefining
our workflow.
The New Features we're liking are:-
Roadmap - Very helpful in communication to non-development types! (as well
as development people too!)
Action To Multiple Bugs - being able to change the target build for multiple
bugs for example is very handy! (as well as all the other action items)
Time Tracking - not 100% working although I am almost there with the config
(I hope.) This would be one of the most beneficial changes if we could get
this implemented correctly.
Manage Configuration - Admin from the admin login. Very nice to be able to
change items like the View Issues page in seconds! Very Nice.
Thanks again Victor!
On 5/22/07, Victor Boctor <[EMAIL PROTECTED]> wrote:
The standard we use at the moment is to have the main issue as the
parent and the ports as child issues (one child issue per target
version). We also prefix the summary of the child issues with
"Port:". I typically use the "Clone Issue" button to create a port
issue from the main issue.
I am thinking eventually we should have "port" as a relationship type.
I am glad you are liking 1.1.0a3. It would be great to know what are
your favorite features :)
On 5/21/07, Shawn Hill <[EMAIL PROTECTED]> wrote:
> Victor,
>
> Thanks for your prompt reply!
>
> You mention a "Port" issue. Would this be a parent issue with the child
> issues, one for each target version?
>
> I'm liking what I see in version 1.1.0a3 by the way. Things are looking
> good!
>
> Kind Regards
>
> Shawn
>
>
>
> On 5/22/07, Victor Boctor <[EMAIL PROTECTED] > wrote:
> >
> > This is a common requirement. My take on this is that you want to be
> > able to target a fix for one or more versions and you also want to
> > track the fixed_in_version to those versions. You would also want to
> > track the status of the issue for each of these versions and
> > potentially the person doing the fix or the port may be different.
> > Hence, the recommended way to do this in Mantis is to create Port
> > issues that point to the original issue. Hence, you can track who is
> > responsible for the main issue and each port, what is the status of
> > each port, what is the target version, the fixed in version, and
> > potentially the CVS/Subversion integration comments.
> >
> > This is also the approach we use to track issues in Mantis that are
> > targeted for both development and stable versions.
> >
> > On 5/21/07, Shawn Hill < [EMAIL PROTECTED]> wrote:
> > > Hi All,
> > >
> > > When will it be possible to have one bug assigned to multiple target
> > > versions? I would like this functionality as I have up to 3
releases
> > > running concurrently. One in Alpha (say Version 3) , one in Beta
(say
> > > Version 2) and one in GA (say Version 1). Should a bug be reported
in
> > > Version 1, I may have to release another build of version 1
depending on
> > > severity of the bug ( e.g. 1.1). This bug will however, need to be
> ported
> > > to Versions 2 and 3. If I could use the Target Version for example,
Bug
> > > 0001 assigned to Versions 1 2 and 3 then I know that it will be
pushed
> into
> > > all versions and this can be seen in the roadmap. Similarly I may
not
> want
> > > the bug fixed in Version 1, I may want it fixed in 2 and 3 only or
even
> only
> > > version 3. The latter is no issue but all other scenarios require
> multiple
> > > target versions.
> > >
> > > Is there a way I can apply a patch in the interim or is this in the
> > > pipeline?
> > >
> > > I am currently running 1.1.0a3
> > >
> > > Many thanks
> > >
> > > Shawn,
> > >
> > > --
> > > [EMAIL PROTECTED]
> > >
>
-------------------------------------------------------------------------
> > > This SF.net email is sponsored by DB2 Express
> > > Download DB2 Express C - the FREE version of DB2 express and take
> > > control of your XML. No limits. Just data. Click to get it now.
> > > http://sourceforge.net/powerbar/db2/
> > > _______________________________________________
> > > mantisbt-help mailing list
> > > [email protected]
> > >
> https://lists.sourceforge.net/lists/listinfo/mantisbt-help
> > >
> > >
> >
> >
>
-------------------------------------------------------------------------
> > This SF.net email is sponsored by DB2 Express
> > Download DB2 Express C - the FREE version of DB2 express and take
> > control of your XML. No limits. Just data. Click to get it now.
> > http://sourceforge.net/powerbar/db2/
> > _______________________________________________
> > mantisbt-help mailing list
> > [email protected]
> >
> https://lists.sourceforge.net/lists/listinfo/mantisbt-help
> >
>
>
>
> --
> [EMAIL PROTECTED]
>
-------------------------------------------------------------------------
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> _______________________________________________
> mantisbt-help mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/mantisbt-help
>
>
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
mantisbt-help mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mantisbt-help
--
[EMAIL PROTECTED]
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
mantisbt-help mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mantisbt-help
