Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: mantisbt/mantisbt
base: d6fc8aa
Choose a base ref
...
head repository: mantisbt/mantisbt
compare: a939b3e
Choose a head ref
  • 2 commits
  • 1 file changed
  • 1 contributor

Commits on Feb 23, 2012

  1. Fix #13935: Version-based filtering not possible 

    Commit a683982 for bug #13096
introduced a regression in version-based filtering due to not properly
dealing with selected version parameter when passed as an array.
    @dregad
    dregad committed Feb 23, 2012
    Copy the full SHA
    57e2005 View commit details
    Browse the repository at this point in the history

  2. Avoid error when editing bug with invalid version 

    When editing an issue having the Product Version field set to a version
number which is not defined in the issue's current project (which can
happen when the issue has been moved from another project, or a version
has been deleted from the current project), APPLICATION ERROR 1601 -
Version "" not found occurs.

The error occurs because the version field in the bug table is not
cleared when the issue is moved, so when Mantis is building the version
selection list to edit the bug, it tries to add the version defined in
it to the list, which triggers the error since that version does not
exist in the current project.

Regression caused by commit 0ffb20f

Fixes #13938
    @dregad
    dregad committed Feb 23, 2012
    Copy the full SHA
    a939b3e View commit details
    Browse the repository at this point in the history