View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0005668 | mantisbt | sub-projects | public | 2005-05-30 11:33 | 2015-05-21 12:47 |
Reporter | polzin | Assigned To | |||
Priority | normal | Severity | minor | Reproducibility | N/A |
Status | acknowledged | Resolution | open | ||
Summary | 0005668: "versions" of parent project should be used in subprojects. | ||||
Description | I would like to simplify the management of several projects that have the same "version" by assigning them to the same parent project. Then the "version" for the filters and for drop-down boxes could use the version numbers of the parent project. Issue 0005599, which is said to be fixed, claims to implement such a thing (at least in my understanding), but it does not do it. It would also be usedful if project-categories can be configured in the same centralised way. | ||||
Additional Information | See also my other report 0005666 on duplicates when version numbers are used the other way around. | ||||
Tags | No tags attached. | ||||
related to | 0011624 | closed | jreese | Updating version name in parent project does not update references in child projects |
has duplicate | 0005669 | closed | thraxisp | "versions" of parent project should be used in subprojects. |
has duplicate | 0007272 | closed | vboctor | Let Sub-Projects inherit the Versions |
has duplicate | 0007942 | closed | vboctor | Subprojects doesn't inherit versions |
has duplicate | 0006147 | closed | vboctor | Inheriting version to subprojects ? |
has duplicate | 0010243 | closed | vboctor | New Feature "Copy Versions to all Subprojects" |
has duplicate | 0014265 | closed | dregad | Cannot filter by Target Version or Fixed In Version over All Projects |
has duplicate | 0016045 | closed | dregad | Version list in bug action group menu |
related to | 0010873 | closed | dregad | Change Log/Roadmap do not work with inherited versions. |
related to | 0012261 | closed | cproensa | Cannot filter by versions of parent project when child project selected |
related to | 0013147 | new | I really want true global versions (like global categories) |
So, i'm too interested by this issue, because it's difficult to manage the version, if i want to add one or more versions in the Parent project,the children project aren't updated and i must do it manually. |
|
Is there a chance, that is could be done? I had a quick look at it, but had the impression that there are to many places that have to be fixed such that it is not feasible for me to fix it myself. |
|
Anybody has an idea on this subject? |
|
I'd the same problem. I build a "quick&dirty" solution in the following way:
Now the combobox on the ChangeStatusPage shows the version numbers of the parental project.
|
|
Thanks for the patch! For my problem, it should be sufficient, anyway it would be good for Mantis, if the usefulness of the project-hierachy would be extended in a consistent manner. Possible issue with the patch: It is not checked, whether the parent project is visible for the user. (Which is good in my situation, as some users don´t "see" the parent project). |
|
Wouldn´t it be better to patch "print_version_option_list", because this will be used also on the bug report page? I tried it and it seems to work, but perhaps anyone sees a problem with this... |
|
Oh, perhaps one should patch "version_get_all_rows", because this is used also on the changelog page... |
|
Ok, done. Perhaps it's better now. It seems to be a good idea to patch the "version_get_all_rows" function, because now the versions are also available in the project management. Now it's also recursive, I think.
$t_parent_id=project_hierarchy_get_parent_id($p_project_id);
} return $rows; The only open issue is the compliance with the user rights (is the project visible?). Maybe someone have an idea for solving it? |
|
Any word on when/if this fix will be added to the core? |
|
I've fixed two things with the patch:
|
|
I have added some more fixes so the change log shows sub-projects properly: In core/version_api.php:
~line 344: changelog_page.php:
|
|
Interested, too. Will this feature be available in official mantis? |
|
This is a very require feature for my. Will this one be available in 1.1.0 release ? |
|
I've an technical solution (idea) for that feature, I need, too: The project_version_table could get an additional boolean column named "use_in_subproject". Thus versions could be managed in the head project and will be available in the subprojects. If subprojects need their own (additional) versions (this could be neccesarry in case of special patches) the subproject could add own version strings. They must be checked against the head project versions to not interfere with them. <b>For issues</b> the versions are not linked, but the text is copied, so this does not interfere the process. <b>For filters</b>: If I'm in the head project, only versions if the head are available for filtering. It might be useful to get a flag ("include sub versions"). If I'm inside a sub project all versions including the head project versions are available then. |
|
I also suggest this patch in core/version_api.php Patch to handle version from parent
END |
|
I have a small change to andreg's last post. Instead of doing the comparison $rows[$j]['version']==$parent_rows[$i]['version'] I suggest using strcmp($rows[$j]['version'], $parent_rows[$i]['version']) == 0 We had a problem where it considered version 4.1 equal to 4.10. Making this change allowed both versions to show up. |
|
thank you all. the patch works fine for me. if you put out of the if statement you get the "original" version also sorted. |
|
if you change a version in a project the versions in the subprojects didn't get updated. to fix this beaviour you have to edit the function version_update in core/versions.php add $t_project_hierarchy_table = config_get( 'mantis_project_hierarchy_table' ); add #select for all project-ids (parent-project and all subprojects) above and now replace project_id='$c_project_id' in the update-where-clauses by project_id IN ($project_id_query) |
|
There are several patches as notes for this issue, but for which version of mantis are the patches to be applied? Its all the same version; the issue does not have any(more) a version information |
|
Does this patches will be included in 1.1 release? |
|
i implement and test it in 1.1.0a4 |
|
This bug has been around for 2.5 years now. vboctor, any chance that this could be assigned and put into 1.2? |
|
Anybody can upload cumulative patch for this issue for Mantis release 1.1.1 ? |
|
I would also be interested in a patch for Mantis 1.1.1! Thanks in advance, |
|
When reporting a bug against a sub-project that has multiple parent projects, how is this handled by the patch? My feeling is that the patch assumes one parent project and hence gets the versions associated with the first version it finds. |
|
Whether this issue will be fixed? |
|
Is it possible to fix this issue in the next release? 1.2.x? |
|
I've checked this in into git trunk. I would appreciate if someone can try it out and give me feedback. |
|
Inheritance is working at first sight, altough the issues do not appear in roadmap/changelog. |
|
test, please ignore. |
|
@aCCuReRaS, can you please provide the steps to reproduce the issue that you found? |
|
Sorry for the delay, but here are the steps:
I hope this helps! |
|
vboctor, can this issue be included in the final 1.2.0? It would make our version handling a lot easier, as we do 1 release each week, for +10 projects in our company. |
|
I second this need. A fix in official 1.2.0 would be nice. |
|
May I kindly ask - is there any progress on that? The management of subprojects is great so far; however as the generated roadmap does not include the subprojects' issues, it lacks a core feature for planning. (our case is similar to what others described: a main project with subprojects, but only the main project shall carry versions. inheritation of the versions works, but the issues don't show up on the roadmap page) Thanks! |
|
Some questions.
|
|
@vboctor. "I've checked this in into git trunk. I would appreciate if someone can try it out and give me feedback." I would love to test, on v1.2.5 stable currently. An I'm able to test have good understanding of Mantis used for some years already. I indeed do have projects with sub-projects where one sub-project is also a sub-project of a another Project. But which version to do a Git Clone? Could you provide the commandline so I'm sure the version I'm cloning is correct. I think http://git.mantisbt.org/?p=mantisbt.git;a=snapshot;h=1e1c073be272d9785065c16b51d455a7f019d133;sf=tgz will also do correct? Thus like: PROJ_A PROJ_B |
|
Goal: A roadmap page which also shows the roadmap of sub-projects on the page I did test it on version 1.2.5 Git of 20110408 an the roadmap worked for sub-projects, Great! I had: PROJ_A PROJ_B Make sure you have:
One of the main thin to keep in mind that a roadmap is a Project bound to Version and Deliverydate. If one has no target version set it will an cannot show in the roadmap ofcourse. If somethisn does not work since you upgraded from older versions then thes things might help:
*Unlink Unlink everythin first, set your version, then relink the sub-project Select allupdate target version of a version in the dropdownNow make it a sub-project again...it works, than good. If id dioes not make sure you understand mantis and roadmap concept well, and try again with a new Project and subproject. Notes: Ensure you have set the config "$g_roadmap_view_threshold" to something good (e.g. VIEWER) |
|
Unfortunately, when I set a subproject as an active project I still cannot use parent versions in filters. It can be seen also in "SubProject 2" subproject of "Mantis Touch" project. |
|
To display all versions of projects parents, I apply the following patches : |
|
Very simple solution! Indeed it gives to much versions on the list (it gives versions of the top parent project and its <u>all</u> subprojects), but it is much much better solution than the original one, which gives incomplete list. Thank you! |
|
There is a easier solution : https://www.mantisbt.org/bugs/view.php?id=12261#c50633 |
|
MantisBT: master 336a964e 2009-07-07 22:07 Details Diff |
Fixes 0005668: versions of parent project should be used in subprojects. |
Affected Issues 0005668 |
|
mod - core/print_api.php | Diff File | ||
mod - docbook/adminguide/en/configuration.sgml | Diff File | ||
mod - manage_proj_edit_page.php | Diff File | ||
mod - view_filters_page.php | Diff File | ||
mod - core/version_api.php | Diff File | ||
mod - core/category_api.php | Diff File | ||
mod - core/prepare_api.php | Diff File | ||
mod - config_defaults_inc.php | Diff File | ||
mod - bug_view_advanced_page.php | Diff File | ||
mod - bug_view_page.php | Diff File | ||
mod - core/filter_api.php | Diff File | ||
mod - manage_proj_page.php | Diff File | ||
mod - print_bug_page.php | Diff File | ||
MantisBT: master-1.2.x 9c4a9b75 2009-07-07 22:07 Details Diff |
Fixes 0005668: versions of parent project should be used in subprojects. |
Affected Issues 0005668 |
|
mod - bug_view_page.php | Diff File | ||
mod - core/print_api.php | Diff File | ||
mod - manage_proj_edit_page.php | Diff File | ||
mod - docbook/adminguide/en/configuration.sgml | Diff File | ||
mod - view_filters_page.php | Diff File | ||
mod - core/version_api.php | Diff File | ||
mod - core/category_api.php | Diff File | ||
mod - print_bug_page.php | Diff File | ||
mod - core/prepare_api.php | Diff File | ||
mod - config_defaults_inc.php | Diff File | ||
mod - core/filter_api.php | Diff File | ||
mod - bug_view_advanced_page.php | Diff File | ||
mod - manage_proj_page.php | Diff File |