I have been using mantis for my own project for a while. It is simple and effective. Thanks.
I an looking for a way to manage features planned for one version.
For example, I plan to
improve manual(Issue #111)
and
change the logo(Issue #112)
in version 4.1.rc1
I have taken a look at mantis' own issues, and it seems that Issue #0004181 is just created for this purpose.
In some issue tracking systems. There is a field called "target version" which can be set for each planned verion.
In my own mantis(Mantis 1.0.0a3), I can't set a "target version" to each issue.
Is it(target version) supported by Mantis? Is it planned?
How to manage Features planned for one version?
Moderators: Developer, Contributor
Re: How to manage Features planned for one version?
This question is post by me. I didn't know that mantis forum allows a "guest" to post message.
I have been using mantis for my own project for a while. It is simple and effective. Thanks.
I an looking for a way to manage features planned for one version.
For example, I plan to
improve manual(Issue 111)
and
change the logo(Issue 112)
in version 4.1.rc1
I have taken a look at mantis' own issues, and it seems that Issue #0004181 is just created for this purpose.
In some issue tracking systems. There is a field called "target version" which can be set for each planned verion.
In my own mantis(Mantis 1.0.0a3), I can't set a "target version" to each issue.
Is it(target version) supported by Mantis? Is it planned?
I have been using mantis for my own project for a while. It is simple and effective. Thanks.
I an looking for a way to manage features planned for one version.
For example, I plan to
improve manual(Issue 111)
and
change the logo(Issue 112)
in version 4.1.rc1
I have taken a look at mantis' own issues, and it seems that Issue #0004181 is just created for this purpose.
In some issue tracking systems. There is a field called "target version" which can be set for each planned verion.
In my own mantis(Mantis 1.0.0a3), I can't set a "target version" to each issue.
Is it(target version) supported by Mantis? Is it planned?
There are two schools of thought on this.
You can use the umbrella issue as we do for Mantis. In this case, each issue is a child of the umbrella parent. This gives a summary of the issues being resolved in the parent issue.
You could also set the fixed-in version early on in the process, when the issue is confirmed. This allows one to use the filter to select all issues in a release.
You can use the umbrella issue as we do for Mantis. In this case, each issue is a child of the umbrella parent. This gives a summary of the issues being resolved in the parent issue.
You could also set the fixed-in version early on in the process, when the issue is confirmed. This allows one to use the filter to select all issues in a release.
Thanks.thraxisp wrote:There are two schools of thought on this.
You can use the umbrella issue as we do for Mantis. In this case, each issue is a child of the umbrella parent. This gives a summary of the issues being resolved in the parent issue.
You could also set the fixed-in version early on in the process, when the issue is confirmed. This allows one to use the filter to select all issues in a release.
I have create a "=versions" custom fields to do this job.