View Issue Details

WikiRelated ChangesetsJump to Notes
IDProjectCategoryView StatusDate SubmittedLast Update
0021030mantisbtsponsorshipspublic2016-05-30 11:582016-06-12 00:42
Reporterdregad Assigned Todregad  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionfixed 
Target Version1.3.0-rc.2Fixed in Version1.3.0-rc.2 
Summary0021030: Error 1704 assigning a sponsored after sponsorship has been turned off
Description

It is not possible to assign a previously sponsored issue even when sponsorship has been switched off:

APPLICATION ERROR 1704
Access Denied: Assigning sponsored issues requires higher access level.

Steps To Reproduce
  • set $g_enable_sponsorship = ON;
  • set $g_assign_sponsored_bugs_threshold = DEVELOPER
  • sponsor an issue
  • disable sponsorship
  • reset $g_assign_sponsored_bugs_threshold to default (MANAGER)
  • try to assign an issue
TagsNo tags attached.

Activities

dregad

dregad

2016-05-31 11:15

developer   ~0053238

PR https://github.com/mantisbt/mantisbt/pull/782

Related Changesets

MantisBT: master 1a4ecfcb

2016-05-31 07:09

dregad


Details Diff		 Do not enforce related thresholds when sponsorship is OFF

When $g_enable_sponsorship = OFF, we should not enforce related
thresholds ($g_handle_sponsored_bugs_threshold and
$g_assign_sponsored_bugs_threshold) when updating issues.

Fixes 0021030		 Affected Issues
0021030
mod - bug_change_status_page.php Diff File
mod - bug_update.php Diff File