View Issue Details

IDProjectCategoryView StatusLast Update
0011041mantisbtbugtrackerpublic2010-02-22 14:34
Reporterdhx Assigned Todhx  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionfixed 
Product Version1.2.0rc2 
Target Version1.2.0Fixed in Version1.2.0 
Summary0011041: set_status_threshold doesn't work on a per-project basis
Description

We currently use access_get_status_threshold() inside access_api.php to do all checks based on the set_status_threshold configuration option. Hence this function works on a global level. It accepts a project ID argument but doesn't actually use it!

What we really need is a new function like access_get_bug_status_threshold that works on a per-bug level, rather than a global "what project have you got selected in the project dropdown" basis.

TagsNo tags attached.

Activities

vboctor

vboctor

2010-01-02 00:47

manager   ~0024020

Moved to 1.3.x, unless @dhx gets to it earlier. It doesn't seem to me like a blocking bug for 1.2.x.

am-gtz

am-gtz

2010-01-27 04:09

reporter   ~0024258

is that fixed now?

from IRC:

dhx_m: I might have it fixed now, just checking

dhx

dhx

2010-01-27 10:57

reporter   ~0024263

Fixed pending a few final tests. Will commit shortly :)

dhx

dhx

2010-01-27 19:58

reporter   ~0024265

Committed to 1.2.x and 1.3.x

Related Changesets

MantisBT: master-1.2.x 9a55e85c

2010-01-27 11:07

dhx


Details Diff
Fix 0011041: set_status_threshold doesn't work on a per-project basis

We currently use access_get_status_threshold() inside access_api.php to
do all checks based on the set_status_threshold configuration option.
Hence this function works on a global level. It accepts a project ID
argument but doesn't actually use it!

This commit also fixes up some issues with the change status option
lists with respect to per-project configuration of set_status_threshold.
Affected Issues
0011041
mod - core/print_api.php Diff File
mod - bug_change_status_page.php Diff File
mod - core/access_api.php Diff File
mod - core/html_api.php Diff File

MantisBT: master c0bdd8c9

2010-01-27 11:07

dhx


Details Diff
Fix 0011041: set_status_threshold doesn't work on a per-project basis

We currently use access_get_status_threshold() inside access_api.php to
do all checks based on the set_status_threshold configuration option.
Hence this function works on a global level. It accepts a project ID
argument but doesn't actually use it!

This commit also fixes up some issues with the change status option
lists with respect to per-project configuration of set_status_threshold.
Affected Issues
0011041
mod - core/access_api.php Diff File
mod - core/print_api.php Diff File
mod - bug_change_status_page.php Diff File
mod - core/html_api.php Diff File