View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0013096 | mantisbt | custom fields | public | 2011-06-22 06:27 | 2014-09-23 18:05 |
| Reporter | jonathh | Assigned To | dregad | ||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Product Version | 1.2.2 | ||||
| Target Version | 1.2.9 | Fixed in Version | 1.2.9 | ||
| Summary | 0013096: Spurious Target Version Behaviour. | ||||
| Description | Hi, if you set a target version in one area that isn't a valid target version for another area the behaviour is not as you would expect. Although the issue appears to have no target version. o) It still appears in searches for that target version (at a higher project level) All of this behaviour although slightly quirky I can forgive as Mantis does not trash fields where valid are not enabled etc. What is not forgiveable is if you EDIT the issue the target version field comes up as blank. If you 'update' having changed something else or not the target version is trash and set to blank; almost certainly unwittingly. Can I have some thoughts on this? It makes more sense to me to trash the value as you move it but warn the user. Or at least warn when the value is trashed (unwittingly) with an idle update. Cheers. | ||||
| Steps To Reproduce |
Target Version has been set to blank (The same behavior applies for other Version fields) | ||||
| Tags | No tags attached. | ||||
| related to | 0015721 | closed | grangeway | Functionality to consider porting to master-2.0.x |
| has duplicate | 0005659 | closed | dregad | Updating an issue causes version to be deleted if version is not marked released |
| related to | 0013935 | closed | dregad | Version based filtering not possible |
| related to | 0013938 | closed | dregad | Error when editing issue having version not existing in current project |
| related to | 0014842 | closed | dregad | Incorrect matching of versions in print_version_option_list() |
 |
@jonathh - I have fixed the so-called "not forgiveable" behavior. With regards to the first part of your bug report, I am not really sure to fully understand what you mean; if you believe that a fix for this is needed, please feel free to reopen this bug and provide clear steps to reproduce the behavior you describe. |
 |
Marking as 'acknowledged' not resolved/closed to track that change gets ported to master-2.0.x branch |
|
MantisBT: master 0ffb20f8 2012-01-10 00:30 Details Diff |
Prevent unwanted clearing version fields when editing bugs When editing issues having Version information set to some value that is no longer available in the selection list (i.e. because the version has been marked as obsolete), Mantis defaulted the corresponding Version field to blank in the bug_update_page. If the user then saved the bug, the version information was consequently cleared in the DB, possibly without the user even noticing the change. This commit ensures that the version selection list always includes the currently set version to avoid this behavior. Fixes 0013096 |
Affected Issues 0013096 |
|
| mod - core/print_api.php | Diff File | ||
|
MantisBT: master-1.2.x a6839824 2012-01-10 00:30 Details Diff |
Prevent unwanted clearing version fields when editing bugs When editing issues having Version information set to some value that is no longer available in the selection list (i.e. because the version has been marked as obsolete), Mantis defaulted the corresponding Version field to blank in the bug_update_page. If the user then saved the bug, the version information was consequently cleared in the DB, possibly without the user even noticing the change. This commit ensures that the version selection list always includes the currently set version to avoid this behavior. Fixes 0013096 |
Affected Issues 0013096 |
|
| mod - core/print_api.php | Diff File | ||
|
MantisBT: master 57e20055 2012-02-21 10:48 Details Diff |
Fix 0013935: Version-based filtering not possible Commit a68398245663d25229800638b6965ffe6e7ab0d3 for bug 0013096 introduced a regression in version-based filtering due to not properly dealing with selected version parameter when passed as an array. |
Affected Issues 0013096, 0013935 |
|
| mod - core/print_api.php | Diff File | ||
|
MantisBT: master-1.2.x 84c6fe6a 2012-02-21 10:48 Details Diff |
Fix 0013935: Version-based filtering not possible Commit a68398245663d25229800638b6965ffe6e7ab0d3 for bug 0013096 introduced a regression in version-based filtering due to not properly dealing with selected version parameter when passed as an array. |
Affected Issues 0013096, 0013935 |
|
| mod - core/print_api.php | Diff File | ||
|
MantisBT: master-1.2.x 14560348 2012-10-18 02:54 Details Diff |
Fix 0014842: Incorrect matching of versions in print_version_option_list When comparing versions to determine which ones have already been added to the select list, a loose comparison is performed, so '1' matches '1.0'. This causes issues when editing a bug having a version currently obsolete matching another, previously displayed version. In that case the obsolete version is not added to the selection list, causing data loss when the bug is saved (see issue 0013096). |
Affected Issues 0013096, 0014842 |
|
| mod - core/print_api.php | Diff File | ||
|
MantisBT: master 62a24e93 2012-10-18 02:54 Details Diff |
Fix 0014842: Incorrect matching of versions in print_version_option_list When comparing versions to determine which ones have already been added to the select list, a loose comparison is performed, so '1' matches '1.0'. This causes issues when editing a bug having a version currently obsolete matching another, previously displayed version. In that case the obsolete version is not added to the selection list, causing data loss when the bug is saved (see issue 0013096). |
Affected Issues 0013096, 0014842 |
|
| mod - core/print_api.php | Diff File | ||
