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

Commits on Dec 6, 2012

  1. access_get_status_threshold() returns incorrect value for NEW 

    When the user's access level is below $g_update_bug_status_threshold and
the status to change to is NEW, the function returned the incorrect
access level, preventing user from accessing the target status when
updating bugs, even though the workflow permits it.

This commit fixes the problem by introducing special handling for NEW
status ('bug_submit_status'), in which case the function returns
'report_bug_threshold' otherwise it falls back to default
'update_bug_status_threshold'.

Fixes #15260, affects issue #15258
    @dregad
    dregad committed Dec 6, 2012
    Copy the full SHA
    179bfc0 View commit details
    Browse the repository at this point in the history

  2. Prevent reporters from changing issue status to 'new' 

    Due to a missing access level check in html_button_bug_update(), in some
cases reporters had access to the 'Change Status To' button, which could
let them change an existing issue's status to 'new' (even if not their
own issue).

The code now checks that the user has at least 'update_bug_threshold'
permissions to display the button.

Fixes #15258
    @dregad
    dregad committed Dec 6, 2012
    Copy the full SHA
    c881373 View commit details
    Browse the repository at this point in the history