Mantis 2.0 - Limitation - customise new status values

General discussion of Mantis.

Moderators: Developer, Contributor

Post Reply
mantisiator
Posts: 16
Joined: 18 Apr 2016, 12:41
Location: Paris, France

Mantis 2.0 - Limitation - customise new status values

Post by mantisiator »

Hi,
I have implemented a list of new status - using the documentation advisories and I think that I have encountered a Limitation (which might be here before version 2.0).
Pratically, all my tests were OK while using admin rights, but when granting the rights to reporter, developper..., problems started to appear.
I have defined the follwong status:

$s_status_enum_string ='5:Bug,7:CRUR,10:New,15:Submitted,50:Assigned,35:Under Work,36:Under Integration,75:Pending,80:Resolved,95:Cancelled,90:Closed,
200:Known,201:Under Approval,202:Not Approved,203:Waiting,204:Fixed,205:Not Fixed,206:Delivered,230:Created,231:On Going,
300:Rejected,301:Approved,302:To be implemented,303:HLA Under Work,304:HLA Approved,305:DLA Under Work,306:DLA Completed,307:Validated'

The problem is that the closed status has value 90, and therefre, when moving issues status to more than this value, the mantis implementation considers that the issue is closed, for instance:

if( $t_existing_bug->status < $t_resolved_status &&
$t_updated_bug->status >= $t_resolved_status &&
$t_updated_bug->status < $t_closed_status
) {
$t_resolve_issue = true;
} else if( $t_existing_bug->status < $t_closed_status &&
$t_updated_bug->status >= $t_closed_status
) {
$t_close_issue = true;
} else if( $t_existing_bug->status >= $t_resolved_status &&
$t_updated_bug->status <= config_get( 'bug_reopen_status' )
) {
$t_reopen_issue = true;
}

Am I wrong when stating that the "new status" values have to be carefully set ?

Thanks a lot in advance !
Post Reply