View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0010388 | mantisbt | feature | public | 2009-04-23 06:53 | 2009-07-04 07:57 |
| Reporter | ruslan | Assigned To | |||
| Priority | normal | Severity | minor | Reproducibility | have not tried |
| Status | feedback | Resolution | open | ||
| Summary | 0010388: RoadMap should respect a PRODUCT LINE | ||||
| Description | Hi, the same Valentina DB mantis site: When I watch RoadMap thinking about Valentina database release 4.2, Right now, I will see say 10 Valentina projects, ANNOYING and not logical. | ||||
| Tags | No tags attached. | ||||
| related to | 0010387 | feedback | PRODUCT LINE / GROUP OF PROJECTS |
|
1.2.0rc1 allows you to click on the project name to filter by a specific product. This can also be done via the URL. Is this what you had in mind? |
|
|
no I think no. PRODUCT LINE -- means ability for us define GROUP of related projects. They should not be always sub-reports. FOR EXAMPLE:
So I want be able specify in mantis that I want be able, define VERSION for the whole product line, but not for EACH separate project as we have now. And we have about 12-15 projects in product line now. Its annoying and error-easy to add for EACH of 15 projects the same version number ... like a monkey :-) Also important is that in ideal case, I can have in the same mantis FEW product lines. Totally different. Not related. Then question is -- what sense in product line ? :-) Just we have catch real life example, when we did try in the same mantis we use for Valentina DB, add few third party projects ... So I watch roadmap for Valentina and see YET that projects ... Even if to assume RULE that single Mantis instal IS a product line self, then still issue with not comfortable VERSION -- one for EACH project . |
|