View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0009829 | mantisbt | roadmap | public | 2008-11-17 18:17 | 2025-09-25 10:02 |
Reporter | baltun | Assigned To | dregad | ||
Priority | normal | Severity | feature | Reproducibility | always |
Status | resolved | Resolution | won't fix | ||
Summary | 0009829: Task, planed in subprojects are part of parent project | ||||
Description | Task, planed in subprojects are part of parent project Versions of subproject should be inherited from parent projects and when task included to planed version, should be added to parent planned version as well. Am I wrong? ?hough it should be an option that enables to do that if turned on, or to do not that if turned off. | ||||
Tags | No tags attached. | ||||
I subscribe this request, when subproject use the same version of main project, we will prefer to have roadmap ordered by version / project, while now is by project / version. Version 1.0 Version 2.0 |
|
Two important things to understand here:
Even though Versions can be copied from the parent to the child Project (or the other way around), they remain independent from each other, even if they bear the same name. So what you are asking cannot be done without a major change to the code base and data model, which is not something we are planning to do, sorry. Closing as won't fix. |
|
Ciao, thank you for your clarification. as you can see in the attached image, we have one main project and many sub-projects.
we cannot change versions in sub-projects do you think that it could be possible to change the roadmap page to change this behaviour justo only if $g_subprojects_inherit_versions is ON? we can try to do that by ourself, if this change do no break the application structure. |
|
Ah sorry I see what you mean now. You're right, I completely forgot about $g_subprojects_inherit_versions config (I don't use subprojects myself). Indeed in this case, in contradiction to what I said in 0009829:0070524, you can use the parent project's versions with the same version ID in the child project.
The logic of roadmap_page.php's is hardcoded, based on 2 nested foreach loops (1. projects, 2. versions). What you want is feasible, but to make it generic (since not everyone will want to do what you are asking), it is not sufficient to rely on g_subprojects_inherit_versions - another config or a UI option on the roadmap page would need to be added to handle the 2 scenarios (projects => versions and versions => projects). Also keep in mind that the project hierarchy can have more than 2 levels (grandchildren, etc), and that the list of projects visible on the Roadmap is constrained by the currently active project (so the version->project mode it would only apply if All projects or a parent project is selected). Honestly I don't think it's worth the effort to implement this, but you're welcome to try. |
|