View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0009408 | mantisbt | feature | public | 2008-07-17 06:38 | 2008-08-12 09:36 |
| Reporter | northstar | Assigned To | vboctor | ||
| Priority | normal | Severity | feature | Reproducibility | N/A |
| Status | closed | Resolution | won't fix | ||
| Product Version | 1.2.0a1 | ||||
| Summary | 0009408: field for "software component" | ||||
| Description | Suggestion : For example, in a Mantis usage scenario where it is used to track bugs/issues within eg. an SAP project, a field such as "software component" would be just right to describe the SAP modules and sub-modules (FI,CO,MM,SD,PP, etc). There are sub-modules under FI such as General Ledger, Accounts Receivables, Accounts Payables, etc (eg. FI - Financial module). Obviously, there is also Sub-project and Category that can be used to describe these SAP modules. One integrated SAP project would consists of multiple modules which cannot be meaningfully defined as sub-projects. Category is really more appropriately used to describe the type of bugs/issues. Of course, custom fields can be created too. Overall, I see that none of these approach will be neater than having a "software component" field. | ||||
| Tags | No tags attached. | ||||