From: Shawn H. <nya...@gm...> - 2007-04-27 03:29:06
|
Hello Everyone, Our company has been using Mantis for some time and we are updating our internal processes and we have a perfect opportunity to get more out of Mantis. I have a couple of questions which I would like your input to please... 1. Categories Do these have any significant meaning in Mantis? I see they are reported on in the Summary pages. Are categories specifically used for functional areas of development, e.g. Installer, GUI, Database etc or can they be used for bug identifiers such as 'Beta Blocker', 'Alpha Bug' etc. or is this not recommended 2. Feature Development Mantis is a bug tracker. Features aren't bugs. Is there a specific, recommended way to deal with new features in Mantis, such as the use of a category 'Feature'? 3. Documentation - workflow Does anyone use mantis to track bugs in documentation. In the example above if we have a new feature, there should be documentation to support it. I would like to work off mantis for the documentation, but I am not sure just yet, as to how to smoothly insert the documentation into the workflow. Could this be a status between resolved and closed? e.g. New Bug Feature->Acknowledged->Assigned->Coded->Resolved->Documented->Closed If anyone has anything to add on the above, comments, suggestions I would be grateful - no seriously I will. In fact so grateful I'll become a serious contributor to mantis somehow. (currently picking up testlink and am contributing there some now!). Besides...it's only fair! Thanks! Shawn -- nya...@gm... |
From: Gerhard F. <li...@co...> - 2007-04-27 14:58:21
|
Shawn Hill wrote: > Mantis is a bug tracker. Features aren't bugs. Just on this one... Mantis can be seen as an issue tracker :) Features are issues, issues are issues, ... We use Mantis to track all kinds of issues; anything that needs to be done or needs a decision or a resolution or a review or ... at a later point in time or by someone else. We don't include documentation in the workflow, we either report a new issue if documentation has to be changed, or assign the issue with an appropriate comment to the one who should write it. (We don't use it in a very formalized manner :) Gerhard |
From: Rich <dvs...@gm...> - 2007-04-27 16:45:45
|
We use a separate "Documentation/text" category for issues with any FAQ, readme etc. this includes issues in-game with text. as for the feature category, it is an issue tracker, we use it to roadmap what we need to finish for release (have separate categories for the different devs=modellers, mapping, code) then I take all the issues that are needed to release and make new issues for them, i have new statuses for the different types (bundlemeshed, skinned, etc for modelling) and then the issue can be assigned to certain people who are working on it. It takes some time to get people working on it, but it works very well. On 4/27/07, Gerhard Fiedler <li...@co...> wrote: > Shawn Hill wrote: > > > Mantis is a bug tracker. Features aren't bugs. > > Just on this one... Mantis can be seen as an issue tracker :) Features are > issues, issues are issues, ... > > We use Mantis to track all kinds of issues; anything that needs to be done > or needs a decision or a resolution or a review or ... at a later point in > time or by someone else. > > We don't include documentation in the workflow, we either report a new > issue if documentation has to be changed, or assign the issue with an > appropriate comment to the one who should write it. (We don't use it in a > very formalized manner :) > > Gerhard > > > ------------------------------------------------------------------------- > 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 > man...@li... > https://lists.sourceforge.net/lists/listinfo/mantisbt-help > -- Rich |
From: Garlitz, J. D <Jef...@vo...> - 2007-04-27 15:12:11
|
Shawn, I am a new user of Mantis and plan to also use the tool to track issues identified during reviews of requirements and test plans that need to be addressed by someone following the review. Can you tell me which functions you use in Mantis to do your tracking? Jeff Garlitz =20 -----Original Message----- From: man...@li... [mailto:man...@li...] On Behalf Of Gerhard Fiedler Sent: Friday, April 27, 2007 10:58 AM To: man...@li... Subject: Re: [mantisbt-help] Correct Use of Mantis Shawn Hill wrote: > Mantis is a bug tracker. Features aren't bugs. =20 Just on this one... Mantis can be seen as an issue tracker :) Features are issues, issues are issues, ... We use Mantis to track all kinds of issues; anything that needs to be done or needs a decision or a resolution or a review or ... at a later point in time or by someone else. We don't include documentation in the workflow, we either report a new issue if documentation has to be changed, or assign the issue with an appropriate comment to the one who should write it. (We don't use it in a very formalized manner :) Gerhard ------------------------------------------------------------------------ - 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 man...@li... https://lists.sourceforge.net/lists/listinfo/mantisbt-help |
From: Shawn H. <nya...@gm...> - 2007-04-28 20:25:56
|
Jeff, I am very mindful about how tools should be used and employed, especially using the right tool for the job. What I am going to do is write a basic list how we use mantis in our organisation, including some of the changes I asked the list about. I also ask the list if it would be a good idea for me to create a document in great detail explaining the use of mantis and some suggested uses of certain areas? We use a wiki to create our requirements using comments and review dates to drive the changes. Test Link will be used to manage test plans. I would strongly recommend reviewing this tool. Firstly we track issues logged by the test team. This is rather simple. The can attach screen shots and shortly will be able to populate the reproduction steps with information directly from a test script in another open source application called TestLink (http://www.teamst.org) . Issues raised here run the normal lifecycle from new to closed. I intend to add a status yet to be named between resolved and closed to ensure that any documentation as a result of a bug gets completed before a bug (or feature) is fully closed. Secondly we track issues logged by support and customers which follows the same rules as above. As you can see Jeff, we don't use mantis to track our requirements or test plans, however, if you were to do this I could suggest the following; Use categories, among others, called 'Requirements' and 'Test Plan'. When there is a requirement for review, a new issue is created with the category of 'Requirements' and any other necessary information for your company, such as assigning it to the person to review, attaching the requirement and the priority etc. and with the status of 'new'. When the person reviewing the requirements picks up the issue they could assign it to themselves, status becomes ' assigned'. If the person reviewing the requirements finds an error they can assign it back to the author with a status of 'feedback' who fixes the issue and uploads the new document and sends it back for review. If it passes review then it can either be resolved or closed. The above can also be done with the use of a 'developer' called 'requirements pool' for example where all new requirements are loaded into a pool and the reviewers pick them off a list by priority -this list can be easily viewed by use of the filters. E.g. View All New issues assigned to 'requirements pool' sorted by priority. Remember that mantis has the ability to predefine and save filters to make this easy. The important thing here Jeff, is to make sure that your work flow fits in with the status and assignments. Have a good look at the reports (making sure jpgraph is installed and working) as this will also give you an indication of what information you can get at the click of a link. Be sure to understand the status' and resolution codes. As this will affect the reports. I have learn't that they key to making mantis work for you is to understand fully the workflow of both mantis and your company. Good luck Jeff, and if you have any more questions, I'll be glad to give you as much information as I can. Mantis is a great tool, enjoy! Shawn On 4/28/07, Garlitz, Jeffrey D <Jef...@vo...> wrote: > > Shawn, > I am a new user of Mantis and plan to also use the tool to track > issues identified during reviews of requirements and test plans that > need to be addressed by someone following the review. Can you tell me > which functions you use in Mantis to do your tracking? > > Jeff Garlitz > > -----Original Message----- > From: man...@li... > [mailto:man...@li...] On Behalf Of > Gerhard Fiedler > Sent: Friday, April 27, 2007 10:58 AM > To: man...@li... > Subject: Re: [mantisbt-help] Correct Use of Mantis > > Shawn Hill wrote: > > > Mantis is a bug tracker. Features aren't bugs. > > Just on this one... Mantis can be seen as an issue tracker :) Features > are > issues, issues are issues, ... > > We use Mantis to track all kinds of issues; anything that needs to be > done > or needs a decision or a resolution or a review or ... at a later point > in > time or by someone else. > > We don't include documentation in the workflow, we either report a new > issue if documentation has to be changed, or assign the issue with an > appropriate comment to the one who should write it. (We don't use it in > a > very formalized manner :) > > Gerhard > > > ------------------------------------------------------------------------ > - > 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 > man...@li... > 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 > man...@li... > https://lists.sourceforge.net/lists/listinfo/mantisbt-help > -- nya...@gm... |
From: Garlitz, J. D <Jef...@vo...> - 2007-04-30 11:29:28
|
Shawn, Thank you very much for your advice on how to use Mantis for tracking issues from requirements and test plan reviews. I really appreciate your suggestions about the use of categories and status for my application. =20 Jeff =20 ________________________________ From: man...@li... [mailto:man...@li...] On Behalf Of Shawn Hill Sent: Saturday, April 28, 2007 4:26 PM To: Help with Mantis Subject: Re: [mantisbt-help] Correct Use of Mantis =20 Jeff, I am very mindful about how tools should be used and employed, especially using the right tool for the job. What I am going to do is write a basic list how we use mantis in our organisation, including some of the changes I asked the list about. I also ask the list if it would be a good idea for me to create a document in great detail explaining the use of mantis and some suggested uses of certain areas? We use a wiki to create our requirements using comments and review dates to drive the changes.=20 Test Link will be used to manage test plans. I would strongly recommend reviewing this tool. Firstly we track issues logged by the test team. This is rather simple. The can attach screen shots and shortly will be able to populate the reproduction steps with information directly from a test script in another open source application called TestLink ( http://www.teamst.org) . Issues raised here run the normal lifecycle from new to closed. I intend to add a status yet to be named between resolved and closed to ensure that any documentation as a result of a bug gets completed before a bug (or feature) is fully closed.=20 Secondly we track issues logged by support and customers which follows the same rules as above. As you can see Jeff, we don't use mantis to track our requirements or test plans, however, if you were to do this I could suggest the following;=20 Use categories, among others, called 'Requirements' and 'Test Plan'. When there is a requirement for review, a new issue is created with the category of 'Requirements' and any other necessary information for your company, such as assigning it to the person to review, attaching the requirement and the priority etc. and with the status of 'new'. When the person reviewing the requirements picks up the issue they could assign it to themselves, status becomes ' assigned'. If the person reviewing the requirements finds an error they can assign it back to the author with a status of 'feedback' who fixes the issue and uploads the new document and sends it back for review. If it passes review then it can either be resolved or closed. The above can also be done with the use of a 'developer' called 'requirements pool' for example where all new requirements are loaded into a pool and the reviewers pick them off a list by priority -this list can be easily viewed by use of the filters. E.g. View All New issues assigned to 'requirements pool' sorted by priority. Remember that mantis has the ability to predefine and save filters to make this easy. The important thing here Jeff, is to make sure that your work flow fits in with the status and assignments. Have a good look at the reports (making sure jpgraph is installed and working) as this will also give you an indication of what information you can get at the click of a link. =20 Be sure to understand the status' and resolution codes. As this will affect the reports. I have learn't that they key to making mantis work for you is to understand fully the workflow of both mantis and your company.=20 Good luck Jeff, and if you have any more questions, I'll be glad to give you as much information as I can. Mantis is a great tool, enjoy! Shawn On 4/28/07, Garlitz, Jeffrey D <Jef...@vo...> wrote: Shawn, I am a new user of Mantis and plan to also use the tool to track issues identified during reviews of requirements and test plans that need to be addressed by someone following the review. Can you tell me=20 which functions you use in Mantis to do your tracking? Jeff Garlitz -----Original Message----- From: man...@li...=20 [mailto:man...@li...] On Behalf Of Gerhard Fiedler Sent: Friday, April 27, 2007 10:58 AM To: man...@li... Subject: Re: [mantisbt-help] Correct Use of Mantis Shawn Hill wrote: > Mantis is a bug tracker. Features aren't bugs. Just on this one... Mantis can be seen as an issue tracker :) Features=20 are issues, issues are issues, ... We use Mantis to track all kinds of issues; anything that needs to be done or needs a decision or a resolution or a review or ... at a later point in time or by someone else.=20 We don't include documentation in the workflow, we either report a new issue if documentation has to be changed, or assign the issue with an appropriate comment to the one who should write it. (We don't use it in=20 a very formalized manner :) Gerhard ------------------------------------------------------------------------ - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take=20 control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ mantisbt-help mailing list=20 man...@li... https://lists.sourceforge.net/lists/listinfo/mantisbt-help=20 ------------------------------------------------------------------------ - 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.=20 http://sourceforge.net/powerbar/db2/ _______________________________________________ mantisbt-help mailing list man...@li... https://lists.sourceforge.net/lists/listinfo/mantisbt-help --=20 nya...@gm...=20 |
From: Garlitz, J. D <Jef...@vo...> - 2007-04-27 20:32:36
|
VGhhbmtzIGZvciB5b3VyIHF1aWNrIHJlc3BvbnNlIGFuZCBpbmZvcm1hdGlvbiBvbiBob3cgeW91 IHVzZSBNYW50aXMuIA0KDQpUaGFua3MsDQpKZWZmDQoNCg0KLS0tLS1PcmlnaW5hbCBNZXNzYWdl LS0tLS0NCkZyb206IG1hbnRpc2J0LWhlbHAtYm91bmNlc0BsaXN0cy5zb3VyY2Vmb3JnZS5uZXQg b24gYmVoYWxmIG9mIFJpY2gNClNlbnQ6IEZyaSA0LzI3LzIwMDcgMTI6NDUgUE0NClRvOiBIZWxw IHdpdGggTWFudGlzDQpTdWJqZWN0OiBSZTogW21hbnRpc2J0LWhlbHBdIENvcnJlY3QgVXNlIG9m IE1hbnRpcw0KIA0KV2UgdXNlIGEgc2VwYXJhdGUgIkRvY3VtZW50YXRpb24vdGV4dCIgY2F0ZWdv cnkgZm9yIGlzc3VlcyB3aXRoIGFueQ0KRkFRLCByZWFkbWUgZXRjLiB0aGlzIGluY2x1ZGVzIGlz c3VlcyBpbi1nYW1lIHdpdGggdGV4dC4NCg0KYXMgZm9yIHRoZSBmZWF0dXJlIGNhdGVnb3J5LCBp dCBpcyBhbiBpc3N1ZSB0cmFja2VyLCB3ZSB1c2UgaXQgdG8NCnJvYWRtYXAgd2hhdCB3ZSBuZWVk IHRvIGZpbmlzaCBmb3IgcmVsZWFzZSAoaGF2ZSBzZXBhcmF0ZSBjYXRlZ29yaWVzDQpmb3IgdGhl IGRpZmZlcmVudCBkZXZzPW1vZGVsbGVycywgbWFwcGluZywgY29kZSkgdGhlbiBJIHRha2UgYWxs IHRoZQ0KaXNzdWVzIHRoYXQgYXJlIG5lZWRlZCB0byByZWxlYXNlIGFuZCBtYWtlIG5ldyBpc3N1 ZXMgZm9yIHRoZW0sIGkgaGF2ZQ0KbmV3IHN0YXR1c2VzIGZvciB0aGUgZGlmZmVyZW50IHR5cGVz IChidW5kbGVtZXNoZWQsIHNraW5uZWQsIGV0YyBmb3INCm1vZGVsbGluZykgYW5kIHRoZW4gdGhl IGlzc3VlIGNhbiBiZSBhc3NpZ25lZCB0byBjZXJ0YWluIHBlb3BsZSB3aG8NCmFyZSB3b3JraW5n IG9uIGl0Lg0KSXQgdGFrZXMgc29tZSB0aW1lIHRvIGdldCBwZW9wbGUgd29ya2luZyBvbiBpdCwg YnV0IGl0IHdvcmtzIHZlcnkgd2VsbC4NCg0KT24gNC8yNy8wNywgR2VyaGFyZCBGaWVkbGVyIDxs aXN0c0Bjb25uZWN0aW9uYnJhemlsLmNvbT4gd3JvdGU6DQo+IFNoYXduIEhpbGwgd3JvdGU6DQo+ DQo+ID4gTWFudGlzIGlzIGEgYnVnIHRyYWNrZXIuICBGZWF0dXJlcyBhcmVuJ3QgYnVncy4NCj4N Cj4gSnVzdCBvbiB0aGlzIG9uZS4uLiBNYW50aXMgY2FuIGJlIHNlZW4gYXMgYW4gaXNzdWUgdHJh Y2tlciA6KSAgRmVhdHVyZXMgYXJlDQo+IGlzc3VlcywgaXNzdWVzIGFyZSBpc3N1ZXMsIC4uLg0K Pg0KPiBXZSB1c2UgTWFudGlzIHRvIHRyYWNrIGFsbCBraW5kcyBvZiBpc3N1ZXM7IGFueXRoaW5n IHRoYXQgbmVlZHMgdG8gYmUgZG9uZQ0KPiBvciBuZWVkcyBhIGRlY2lzaW9uIG9yIGEgcmVzb2x1 dGlvbiBvciBhIHJldmlldyBvciAuLi4gYXQgYSBsYXRlciBwb2ludCBpbg0KPiB0aW1lIG9yIGJ5 IHNvbWVvbmUgZWxzZS4NCj4NCj4gV2UgZG9uJ3QgaW5jbHVkZSBkb2N1bWVudGF0aW9uIGluIHRo ZSB3b3JrZmxvdywgd2UgZWl0aGVyIHJlcG9ydCBhIG5ldw0KPiBpc3N1ZSBpZiBkb2N1bWVudGF0 aW9uIGhhcyB0byBiZSBjaGFuZ2VkLCBvciBhc3NpZ24gdGhlIGlzc3VlIHdpdGggYW4NCj4gYXBw cm9wcmlhdGUgY29tbWVudCB0byB0aGUgb25lIHdobyBzaG91bGQgd3JpdGUgaXQuIChXZSBkb24n dCB1c2UgaXQgaW4gYQ0KPiB2ZXJ5IGZvcm1hbGl6ZWQgbWFubmVyIDopDQo+DQo+IEdlcmhhcmQN Cj4NCj4NCj4gLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0KPiBUaGlzIFNGLm5ldCBlbWFpbCBpcyBzcG9uc29y ZWQgYnkgREIyIEV4cHJlc3MNCj4gRG93bmxvYWQgREIyIEV4cHJlc3MgQyAtIHRoZSBGUkVFIHZl cnNpb24gb2YgREIyIGV4cHJlc3MgYW5kIHRha2UNCj4gY29udHJvbCBvZiB5b3VyIFhNTC4gTm8g bGltaXRzLiBKdXN0IGRhdGEuIENsaWNrIHRvIGdldCBpdCBub3cuDQo+IGh0dHA6Ly9zb3VyY2Vm b3JnZS5uZXQvcG93ZXJiYXIvZGIyLw0KPiBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fXw0KPiBtYW50aXNidC1oZWxwIG1haWxpbmcgbGlzdA0KPiBtYW50aXNi dC1oZWxwQGxpc3RzLnNvdXJjZWZvcmdlLm5ldA0KPiBodHRwczovL2xpc3RzLnNvdXJjZWZvcmdl Lm5ldC9saXN0cy9saXN0aW5mby9tYW50aXNidC1oZWxwDQo+DQoNCg0KLS0gDQpSaWNoDQoNCi0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0NClRoaXMgU0YubmV0IGVtYWlsIGlzIHNwb25zb3JlZCBieSBEQjIgRXhw cmVzcw0KRG93bmxvYWQgREIyIEV4cHJlc3MgQyAtIHRoZSBGUkVFIHZlcnNpb24gb2YgREIyIGV4 cHJlc3MgYW5kIHRha2UNCmNvbnRyb2wgb2YgeW91ciBYTUwuIE5vIGxpbWl0cy4gSnVzdCBkYXRh LiBDbGljayB0byBnZXQgaXQgbm93Lg0KaHR0cDovL3NvdXJjZWZvcmdlLm5ldC9wb3dlcmJhci9k YjIvDQpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KbWFu dGlzYnQtaGVscCBtYWlsaW5nIGxpc3QNCm1hbnRpc2J0LWhlbHBAbGlzdHMuc291cmNlZm9yZ2Uu bmV0DQpodHRwczovL2xpc3RzLnNvdXJjZWZvcmdlLm5ldC9saXN0cy9saXN0aW5mby9tYW50aXNi dC1oZWxwDQoNCg== |
From: Glenn H. <thr...@lo...> - 2007-04-28 01:55:55
|
On 26-Apr-07, at 11:29 PM, Shawn Hill wrote: > Hello Everyone, > > Our company has been using Mantis for some time and we are updating > our internal processes and we have a perfect opportunity to get > more out of Mantis. I have a couple of questions which I would > like your input to please... > > 1. Categories > Do these have any significant meaning in Mantis? I see they are > reported on in the Summary pages. Are categories specifically used > for functional areas of development, e.g. Installer, GUI, Database > etc or can they be used for bug identifiers such as 'Beta Blocker', > 'Alpha Bug' etc. or is this not recommended Bugs in different categories can be automatically assigned to an individual user (otherwise, they are left unassigned. I've used categories as you describe for projects, where all of the staff working on the project are on the project team. If you need to separate access for the individual elements (e.g., coders can't see documentation bugs), upi may want to use separate projects, or sub- projects. > > 2. Feature Development > Mantis is a bug tracker. Features aren't bugs. Is there a > specific, recommended way to deal with new features in Mantis, such > as the use of a category 'Feature'? There is a severity called "feature". > > 3. Documentation - workflow > Does anyone use mantis to track bugs in documentation. In the > example above if we have a new feature, there should be > documentation to support it. I would like to work off mantis for > the documentation, but I am not sure just yet, as to how to > smoothly insert the documentation into the workflow. Could this be > a status between resolved and closed? e.g. > New Bug Feature->Acknowledged->Assigned->Coded->Resolved- > >Documented->Closed You can now have separate workflow on a per project basis. This may affect the choice of categories or projects. The only issue you may have with this workflow would be the handoff between users (coder vs writer). > > If anyone has anything to add on the above, comments, suggestions I > would be grateful - no seriously I will. In fact so grateful I'll > become a serious contributor to mantis somehow. (currently picking > up testlink and am contributing there some now!). Besides...it's > only fair! > Any help would be welcome. -- Glenn Henshaw Logical Outcome Ltd. e: thr...@lo... w: www.logicaloutcome.ca Mantis Developer and User |
From: Jeferson O. <jef...@gm...> - 2007-05-02 20:27:35
|
Hi shawn, Shawn Hill" escreveu: > 3. Documentation - workflow > Does anyone use mantis to track bugs in documentation. In the example above > if we have a new feature, there should be documentation to support it. I > would like to work off mantis for the documentation, but I am not sure just > yet, as to how to smoothly insert the documentation into the workflow. > Could this be a status between resolved and closed? e.g. > New Bug Feature->Acknowledged->Assigned->Coded->Resolved->Documented->Closed I think so. I'm now in a similar situation. In the company workflow at this moment after a developer has finished his job the issue's status is changed to Resolved. All issues in the Resolved status are submitted to the approval of the test team. If the test team find some problem the status is changed to Feedback, if they don't find any problem the issue is closed. After it has been closed it is ready to be included in the release version. This workflow has some probems, because we can't know which issues: - were tested; - were documented; - were indeed included in the release version; I'm planning to create three new status, so the workflow would be: New (Bug/Feature)->Confirmed/Acknowledged->Assigned->Resolved->Tested->Documented->Released->Closed Well, this enlargement of the workflow is worrying me. :) But we really need to have a better view over the process. Any comments are welcome. Regards, Jeferson Oliveira Brazil |
From: John T. <jo...@pi...> - 2007-05-03 13:04:35
|
Hello all, I am attempting to over-ride the bug_delete() function by creating my custom_function_override_bug_delete($bug_id) in the custom_functions_inc.php file. However, it doesn't over ride it. What is the correct procedure for over-riding standard functions? Thanks, John. www.pinesoft.co.uk Pinesoft Computers are registered in England, Registered number: 2914825. Registered office: 266-268 High Street, Waltham Cross, Herts, EN8 7EA This message has been scanned for viruses by BlackSpider MailControl - www.blackspider.com |
From: Vincent D. <de...@fr...> - 2007-05-03 13:12:07
|
> Hello all, Hello, > I am attempting to over-ride the bug_delete() function by creating my > custom_function_override_bug_delete($bug_id) in the > custom_functions_inc.php file. > > However, it doesn't over ride it. > > What is the correct procedure for over-riding standard functions? bug_delete is not a function that you can override. Sorry. Vincent -- Mantis Plugins: <http://deboutv.free.fr/mantis/> |
From: John T. <jo...@pi...> - 2007-05-03 13:27:08
|
Vincent DEBOUT wrote: >> Hello all, >> > > Hello, > > >> I am attempting to over-ride the bug_delete() function by creating my >> custom_function_override_bug_delete($bug_id) in the >> custom_functions_inc.php file. >> >> However, it doesn't over ride it. >> >> What is the correct procedure for over-riding standard functions? >> > > bug_delete is not a function that you can override. Sorry. > > Vincent > > Ok, thanks. Is there a list of those I can/can't override? John www.pinesoft.co.uk Pinesoft Computers are registered in England, Registered number: 2914825. Registered office: 266-268 High Street, Waltham Cross, Herts, EN8 7EA This message has been scanned for viruses by BlackSpider MailControl - www.blackspider.com |
From: Vincent D. <de...@fr...> - 2007-05-03 13:32:41
|
> Vincent DEBOUT wrote: >>> Hello all, >>> >> >> Hello, >> >> >>> I am attempting to over-ride the bug_delete() function by creating my >>> custom_function_override_bug_delete($bug_id) in the >>> custom_functions_inc.php file. >>> >>> However, it doesn't over ride it. >>> >>> What is the correct procedure for over-riding standard functions? >>> >> >> bug_delete is not a function that you can override. Sorry. >> >> Vincent >> >> > Ok, thanks. > > Is there a list of those I can/can't override? Yes, the list is in the core/custom_function_api.php file. Vincent -- Mantis Plugins: <http://deboutv.free.fr/mantis/> |
From: Shawn H. <nya...@gm...> - 2007-05-07 19:12:37
|
Hi Jeferson, While the extra workflow items you mention may worry you, I think after the investigation I have done for our company the benefits of this change outweigh the work required to add the statuses. There is a lot of documentation and information around as to how to change the statuses, so have a read and have a try on a test system beforehand. Another Tip I have is to use a wiki (or something similar) to closely document your changes. The reason for this is at upgrade time you want to be sure that all your customisations are ported across or at least reintroduced on your upgraded system. Mantis has a fantiastic system in the config_inc but there are some bigger changes that are'nt maintained in this way and the statuses at this time is not kept there. I hope I have helped in some way at least, good luck! Shawn. On 5/3/07, Jeferson Oliveira <jef...@gm...> wrote: > > Hi shawn, > > Shawn Hill" escreveu: > > 3. Documentation - workflow > > Does anyone use mantis to track bugs in documentation. In the example > above > > if we have a new feature, there should be documentation to support > it. I > > would like to work off mantis for the documentation, but I am not sure > just > > yet, as to how to smoothly insert the documentation into the workflow. > > Could this be a status between resolved and closed? e.g. > > New Bug > Feature->Acknowledged->Assigned->Coded->Resolved->Documented->Closed > > I think so. > I'm now in a similar situation. > In the company workflow at this moment after a developer has finished > his job the issue's status is changed to Resolved. All issues in the > Resolved status are submitted to the approval of the test team. If the > test team find some problem the status is changed to Feedback, if they > don't find any problem the issue is closed. After it has been closed > it is ready to be included in the release version. > This workflow has some probems, because we can't know which issues: > - were tested; > - were documented; > - were indeed included in the release version; > > I'm planning to create three new status, so the workflow would be: > New > (Bug/Feature)->Confirmed/Acknowledged->Assigned->Resolved->Tested->Documented->Released->Closed > > Well, this enlargement of the workflow is worrying me. :) But we > really need to have a better view over the process. > > Any comments are welcome. > > > Regards, > > Jeferson Oliveira > Brazil > > ------------------------------------------------------------------------- > 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 > man...@li... > https://lists.sourceforge.net/lists/listinfo/mantisbt-help > -- nya...@gm... |
From: Jeferson O. <jef...@gm...> - 2007-05-08 12:45:13
|
"Shawn Hill" escreveu: > Hi Jeferson, Hi Shawn, > Another Tip I have is to use a wiki (or something similar) to closely > document your changes. We have all changes documented in text file. A wiki page will be even better. > I hope I have helped in some way at least You did. ;) Thanks! Jeferson Oliveira Brazil |