View Issue Details

IDProjectCategoryView StatusLast Update
0009829mantisbtroadmappublic2025-09-25 10:02
Reporterbaltun Assigned Todregad  
PrioritynormalSeverityfeatureReproducibilityalways
Status resolvedResolutionwon't fix 
Summary0009829: 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.

TagsNo tags attached.

Activities

simonegirlanda

simonegirlanda

2025-09-25 04:37

reporter   ~0070523

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
main project task
subproject 1 tasks
subproject 2 tasks
....

Version 2.0
main project task
subproject 1 tasks

dregad

dregad

2025-09-25 06:40

developer   ~0070524

Two important things to understand here:

  1. There is a parent-child relationship between Project and Versions.
  2. Versions are not inherited from parent Projects.

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.

simonegirlanda

simonegirlanda

2025-09-25 08:55

reporter   ~0070525

Last edited: 2025-09-25 08:56

Ciao, thank you for your clarification.

as you can see in the attached image, we have one main project and many sub-projects.
sub-projects inherit version of the main project, because of this configuration:

$g_subprojects_enabled = ON;
$g_subprojects_inherit_versions = ON;
$g_subprojects_inherit_categories = ON;

we cannot change versions in sub-projects
version in subprojects has the same id of the main project one.

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.

dregad

dregad

2025-09-25 10:02

developer   ~0070526

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.

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?

The logic of roadmap_page.php's is hardcoded, based on 2 nested foreach loops (1. projects, 2. versions).
See https://github.com/mantisbt/mantisbt/blob/36dabecca295787ae6612fdfbf87d5d89a15f35c/roadmap_page.php#L358-L371

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.