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: a5708e0
Choose a base ref
...
head repository: mantisbt/mantisbt
compare: 0ffb20f
Choose a head ref
  • 2 commits
  • 4 files changed
  • 1 contributor

Commits on Jan 10, 2012

  1. Prevent selection of released version as target 

    If a version has been released, one should not be able to assign new
issues to it. This applies when reporting and updating bugs (including
group updates).

Fixes #11706
    @dregad
    dregad committed Jan 10, 2012
    Copy the full SHA
    0e8f0e2 View commit details
    Browse the repository at this point in the history

  2. 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 #13096
    @dregad
    dregad committed Jan 10, 2012
    6
    Copy the full SHA
    0ffb20f View commit details
    Browse the repository at this point in the history