View Issue Details

WikiRelated ChangesetsJump to Notes
IDProjectCategoryView StatusDate SubmittedLast Update
0011641mantisbtbugtrackerpublic2010-03-10 13:232010-04-23 14:30
ReporterBithunter Assigned Tojreese  
PrioritynormalSeveritymajorReproducibilityalways
Status closedResolutionfixed 
Product Version1.2.0 
Target Version1.2.1Fixed in Version1.2.1 
Summary0011641: Updating version name in project should update issues history
Description

When updating version names in a parent project, version references are not updated for issue's history.

Steps To Reproduce

Create project 1 with version A
Solve some issue in that version
Change version from A to B
Issue history shows "resolved en version A" when should say ""resolved en version B"

TagsNo tags attached.

Relationships

Relationship GraphDependency Graph
related to 0011624 closedjreese Updating version name in parent project does not update references in child projects 

Activities

jreese

jreese

2010-04-22 14:21

reporter   ~0025207

Fix committed to 1.2.x and master branches.

Related Changesets

MantisBT: master-1.2.x cc1ad704

2010-04-22 14:15

jreese


Details Diff		 Fix 0011641: Update history table on version rename

When a version is renamed, existing bug history entries should be
updated with the new version name, including history entries for bugs
from subprojects in the case where versions are inherited from parents.

This has the same potential edge case as previous commits in this area,
such that any child project that contains a duplicate version name will
have entries updated in that child project even if that's not the
desired behavior. However, this is the best option until versions can
be migrated to using integer IDs the same as categories were.		 Affected Issues
0011641
mod - core/version_api.php Diff File

MantisBT: master 3485b702

2010-04-22 14:15

jreese


Details Diff		 Fix 0011641: Update history table on version rename

When a version is renamed, existing bug history entries should be
updated with the new version name, including history entries for bugs
from subprojects in the case where versions are inherited from parents.

This has the same potential edge case as previous commits in this area,
such that any child project that contains a duplicate version name will
have entries updated in that child project even if that's not the
desired behavior. However, this is the best option until versions can
be migrated to using integer IDs the same as categories were.		 Affected Issues
0011641
mod - core/version_api.php Diff File