0011041: set_status_threshold doesn't work on a per-project basis - MantisBT

Mantis Bug Tracker

View Issue Details [ Jump to Notes ] [ Wiki ] [ Related Changesets ]

[ Issue History ] [ Print ]

ID

Project

Category

View Status

Date Submitted

Last Update

0011041

mantisbt

bugtracker

public

2009-10-14 09:51

2010-02-22 14:34

Reporter

dhx

Assigned To

dhx

Priority

normal

Severity

minor

Reproducibility

always

Status

closed

Resolution

fixed

Platform

OS

OS Version

Product Version

1.2.0rc2

Target Version

1.2.0

Fixed in Version

1.2.0

Summary

0011041: 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.

Tags

No tags attached.

Relationships

Notes
(0024020) vboctor (administrator) 2010-01-02 00:47	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.

(0024258) am-gtz (reporter) 2010-01-27 04:09	is that fixed now? from IRC: dhx_m: I might have it fixed now, just checking

(0024263) dhx (developer) 2010-01-27 10:57	Fixed pending a few final tests. Will commit shortly :)

(0024265) dhx (developer) 2010-01-27 19:58	Committed to 1.2.x and 1.3.x

Related Changesets
MantisBT: master-1.2.x 9a55e85c Timestamp: 2010-01-27 16:07:35 Author: dhx Committer: David Hicks [ 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.
	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 Timestamp: 2010-01-27 16:07:35 Author: dhx Committer: David Hicks [ 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.
	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 ]

Issue History
Date Modified	Username	Field	Change
2009-10-14 09:51	dhx	New Issue
2009-10-14 09:51	dhx	Status	new => confirmed
2010-01-02 00:47	vboctor	Note Added: 0024020
2010-01-02 00:47	vboctor	Target Version	1.2.x => 1.3.x
2010-01-27 04:09	am-gtz	Note Added: 0024258
2010-01-27 10:57	dhx	Note Added: 0024263
2010-01-27 10:57	dhx	Assigned To	=> dhx
2010-01-27 10:57	dhx	Target Version	1.3.x => 1.2.x
2010-01-27 10:57	dhx	Status	confirmed => assigned
2010-01-27 19:58	dhx	Note Added: 0024265
2010-01-27 19:58	dhx	Status	assigned => resolved
2010-01-27 19:58	dhx	Fixed in Version	=> 1.2.x
2010-01-27 19:58	dhx	Resolution	open => fixed
2010-01-27 20:00	dhx	Changeset attached	master-1.2.x 9a55e85c =>
2010-01-27 20:00	dhx	Changeset attached	master c0bdd8c9 =>
2010-02-22 14:34	jreese	Status	resolved => closed

MantisBT 1.2.2 git master-1.2.x[^]

Copyright © 2000 - 2010 MantisBT Group

Time: 0.2160 seconds.
memory usage: 1,968 KB