View Issue Details

IDProjectCategoryView StatusLast Update
0035078mantisbtbugtrackerpublic2024-12-30 11:06
Reportermfzleman Assigned Todregad  
PrioritynormalSeverityminorReproducibilitysometimes
Status closedResolutionno change required 
Product Version2.26.3 
Summary0035078: Unable to reopen the issue
Description

Hi!

I am having an issue where i am not able to select 'reopened' resolution whenever i want to reopen my issue and it will appear this kind of error.

my custom setting for status as below:

a. file custom_strings_inc.php
$s_status_enum_string = '10:New,20:Assigned,30:In Progress,40:Testing Level 1,50:Testing Level 2,60:Resolve,70:Close';

b. file config_inc.php
$g_status_enum_string = '10:New,20:Assigned,30:In Progress,40:Testing Level 1,50:Testing Level 2,60:Resolve,70:Close';

Steps To Reproduce

Step 1 - Select issue
Step 2 - Change issue status to Resolve
Step 3 - Select resolution to reopened

TagsNo tags attached.
Attached Files
image.png (29,076 bytes)   
image.png (29,076 bytes)   

Relationships

related to 0015653 closeddregad APPLICATION ERROR 1303 when trying to reopen an issue 

Activities

dregad

dregad

2024-12-04 06:41

developer   ~0069534

Think of Resolution as a sub-Status; the two fields are linked. It does not semantically make sense for an Issue to be resolved and reopened at the same time, and this is the reason why you get this error.

Resolved issues normally have a Reopen button (see screenshot, actual visibility depends on $g_reopen_bug_threshold and $allow_reporter_reopen), which will change the status to $g_bug_reopen_status and set the Resolution to reopened ($g_bug_reopen_resolution).

This is the implemented logic - refer to 0015653 for further details (particularly note 0015653:0037180:

Don't allow changing the Resolution in the following cases:

  • new status < RESOLVED and resolution denoting completion (>= fixed_threshold)
  • new status >= RESOLVED and resolution < fixed_threshold
  • resolution = REOPENED and current status < RESOLVED and new status >= RESOLVED

This is not a bug, resolving as no change required.

image-2.png (6,236 bytes)   
image-2.png (6,236 bytes)