View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0010873 | mantisbt | roadmap | public | 2009-08-25 10:25 | 2015-05-18 11:21 |
Reporter | andy_mbt | Assigned To | dregad | ||
Priority | normal | Severity | major | Reproducibility | always |
Status | closed | Resolution | fixed | ||
Product Version | 1.2.15 | ||||
Target Version | 1.2.16 | Fixed in Version | 1.2.16 | ||
Summary | 0010873: Change Log/Roadmap do not work with inherited versions. | ||||
Description | Basically making an issue for: 0005668:0022460 When using the new version inheritance feature, issues are no longer populating the Change Log and Roadmap. | ||||
Steps To Reproduce |
| ||||
Tags | No tags attached. | ||||
related to | 0005668 | acknowledged | "versions" of parent project should be used in subprojects. | |
related to | 0011402 | closed | dhx | SYSTEM WARNING: in_array() [function.in-array]: Wrong datatype for second argument |
has duplicate | 0011430 | closed | dhx | The bug in the subproject is not in the roadmap |
has duplicate | 0012189 | closed | Subprojects using Parent project versions don't have roadmaps | |
has duplicate | 0012769 | closed | atrol | Change log does not list tickets from sub-projects |
has duplicate | 0014392 | closed | dregad | Change log pag is blank/empty after migration! |
has duplicate | 0017732 | closed | dregad | Change Log and Roadmap don't correctly propagate versions to sub-projects |
related to | 0014637 | acknowledged | Roadmap should not display versions defined in parent siblings ( parent's have some common sub-projects ) |
I have seen the same thing. I migrated my project from 1.2RC1 to 1.2RC2 and cleaned up the versions. Now the roadmap is gone. I will try to find out what is happening in detail. |
|
I have seen this in 1.2RC2 (The roadmap for a subproject does not include an inherited version). I looked at the code and found that this was a caching issue. After commenting out the cache check at the start of version_get_all_rows() (version_api.php) I attained the expected(?) behaviour. Hope that helps anyone trying to fix it. |
|
I followed what you said neilc, unfortunately that only solved one of the two. I can now see the Change Log but still can't see anything under Roadmap. Any other ideas? |
|
When retesting this defect it is important to make sure you do not set the "Released" option to on, if release means, it will not be on the roadmap, since it is , ahum ...released. |
|
Can someone please retest this with the latest git checkout of 1.2.x or 1.3.x? neilc commented above about a caching issue that I should have hopefully fixed as part of 0011402 |
|
Still doesn't work with nightly build as of 2010-01-22. A quick fix is to comment out the invocation of version_cache_array_rows() in roadmap_page.php and changelog_page.php. However, as neilc commented above, the main problem seems to be in core/version_api.php:version_get_all_rows() where very different things are done depending on whether versions are cached or not. |
|
Still doesn't work with nightly build as of 2010-01-25,see http://www.mantisbt.org/bugs/view.php?id=11430 |
|
Tested with the latest 1.2 nightly, roadmap is still empty for sub-project issue. |
|
I just tested this with 1.3.0dev-2010-03-24 and still a no go. Both the roadmap and the changelog do not show sub-project issues where the version is inherited from the parent project. |
|
Can the target version be changed to the next release which I assume will still be one of the 1.2.x versions? |
|
Replacing this issue with bug 0011802 since the other one has a patch attached. |
|
Apologies for the bug noise, was looking at the wrong bug. |
|
Solution? 1) If replace version_get_all_rows in roadmap_page.php, SELECT versions.* Requirements: 1.A) versions.version is unique index, OR 1.B) New field: bug_table.target_version_id INT UNSIGNED ====== OR ======= 2) Synchronize versions table 2.1) New field: versions.parent_id INT UNSIGNED NOT NULL DEFAULT 0 2.2) Inssue, On change target-version, 2.3) Manage Project, list versions WHERE parent_id = 0 2.4) Manage Project, after edit version, ====== Foo project - Foo1.0 |
|
Solution 3: disable get versions from cache /core/version_api.php It solves, i.e., we have a problem in caching results. |
|
@neosonicxmantis (aka hero): Solution 3 works fine with 1.2.0 as well. many thanks! |
|
Confirmed that solution 3 displays the information. I think it should be grouped by milestone though rather than by project/subproject, but I'm happy to open another bug for that. |
|
Solution 3 outlined in 0010873:0026242 worked great for me, on 1.2.1. Thanks for the suggestion ! Update: this fix causes bugs to be displayed twice when displaying the roadmap for a child project (one for the parent, and one for the child). When displaying the roadmap for the parent, the same behavior can be observed, for each of the child projects (i.e. parent has one bug list per upcoming version, and each child has 2) Example: Assuming parent project "P" has child project "C", and C is set to inherit versions from P, the Roadmap for C looks like this: C - Roadmap C - 2.1 (Scheduled For Release 2011-01-10)(list of issues for C in release 2.1) P - 2.1 (Scheduled For Release 2011-01-10)(list of issues, identical to above) |
|
Are there any news on that issue? Is that somehow scheduled or is someone already working on that? |
|
I have the same problem with 1.2.4 does someone know if it is fixed? Roadmapping and change log works fine when you have no subprojects. Since we have a lot of products and new development activity's i would like to use sub projects. |
|
The proposed solution that the caching for the getting the projects associated with the version worked for me also, I didn't understand why the child projects are not added in cache for a specific version, I'll investigate this. Here is the quick fix: Solution 3: disable get versions from cache /core/version_api.php |
|
Confirmed that the quick fix in 0010873:0028392 fixes the display for me |
|
Even though this is more a workaround than fixing the actual caching problem, can the commenting out fix be put in the next 1.2.x release? It's a pain having to remember to re-implement this and is a fairly major bug for those of us using subprojects! (Maybe this bug could be resolved and a new one created for fixing the caching?) |
|
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) |
|
it does not work in our installation. We today installed 1.2.6. On project A I defined a version "test". I created a subproject B and connected it to A (including inheritance). Finally I created an issue under B and fixed in the inherited version "test" (also setting the target version). In another project we have no subprojects and are using versions; here, I can view the roadmap and changelog as in this site. There is still something wrong... |
|
Solution 3 works fine for 1.2.7 as well. Thanks |
|
This would be good to fix in next 1.2.x relase also |
|
Still an issue in my tracker (1.2.8). A fix was mentioned in http://www.mantisbt.org/bugs/view.php?id=10873#c26622 but then http://www.mantisbt.org/bugs/view.php?id=10873#c26622 occurred. Why not, then hold a list of all mentioned bug IDs on the page in a cache? I'll see if I can make a patch to the master branch today. |
|
Solution 3 was a great improvement for my users on 1.2.10 as well. My only problem is the road map displaying versions from a parent's sibling when the other parent is selected before displaying road map. I created issue 0014637 for this. |
|
I, too, would love to see a fix for this. I'm just getting into doing target versions and roadmaps, and this bug makes having a project hierarchy break my roadmaps completely. If I'm looking at the roadmap for a parent project, and a version in the parent project is used as a target for an issue in a sub-project, then that sub-issue should appear in the roadmap. (Right? Is this controversial?) |
|
The scenario as described by dtgriscom I do not think is controversial. The "solution 3" fix provided by gma in one of the notes above provides a work-around to implement this feature. I would enjoy seeing a solution in 1.3.x for the scenario described by dregad in issue 0014637 : "Roadmap should not display versions defined in parent siblings ( parent's have some common sub-projects )" -Ed |
|
I have a very simple fix for this. Additional to 0010873:0028392 I added an simple skip logic for already shown bugs: if(in_array($t_row['id'], $arDisplayedBugs) == true) $arDisplayedBugs[] = $t_row['id']; |
|
I am upgrading from 1.2.6 to 1.2.14 tonight and transferring my local copy of "solution 3" as I found it necessary for the same reason as everyone else. mmmichael, any chance you can provide a context diff so I can be sure I'm putting the code in exactly the right place? thx |
|
Root cause of all these problems relating to the road map is that the version is not properly stored in the bug_table. It is stored as a string and this makes it very difficult to find the real version. In my opinion it should be the version id. Is there anyway to run an automated upgrade script? Example when this is a problem. I have project A with sub project B, both have a version 0.1, then the bug will be assigned to project A 0.1 but will also show up in project B 0.1 It seems that the whole idea of version inheritance is a bit flawed, I can not imagine a proper usage. Either you have all versions defined in the parent or all version per project, a mixture seems a recipe for disaster. |
|
I agree with you that how we currently deal with versions and inheritance is clunky (at best). However, refactoring this is no small undertaking, and an automated upgrade script would be quite complex and is highly likely to encounter issues trying to determine which issue id to use, especially in the cases where we have multiple versions with the same name, combined with the notion of inheritance. |
|
I have submitted a fix to github that leaves the caching mechanism intact. https://github.com/uncletall/mantisbt/commit/5d79b2785f9bd472d1da84d0e26950b3f98639d9 |
|
Thanks for the pull request, I will have a look as time allows |
|
Thanks for your patch Peter, I've merged it in. |
|
MantisBT: master-1.2.x 11cc5daf 2013-06-24 17:58 Committer: dregad Details Diff |
(issue 0010873) Fixes missing version on roadmap Bugs with a target version that is inherited from a parent project are not shown on the roadmap. This fixes this and leaves the caching feature intact. |
Affected Issues 0010873 |
|
mod - core/version_api.php | Diff File | ||
MantisBT: master fa979d8a 2013-09-29 13:33 Details Diff |
Fix 0010873: version inheritance in roadmap and changelog Bugs with a target version that is inherited from a parent project are not shown on the roadmap. This fixes this and leaves the caching feature intact. Many thanks to Peter Bruin for providing a fix for this long-standing issue. |
Affected Issues 0010873 |
|
mod - core/version_api.php | Diff File | ||
mod - library/adodb | Diff File | ||
MantisBT: master-1.2.x 88045cf0 2013-10-21 13:43 Details Diff |
Fix 0010873: version inheritance in roadmap and changelog Many thanks to Peter Bruin for providing a fix for this long-standing issue. |
Affected Issues 0010873 |
|
mod - core/version_api.php | Diff File |