View Issue Details

IDProjectCategoryView StatusLast Update
0011661mantisbtadministrationpublic2014-09-23 18:05
Reporterllattan Assigned Todregad  
PrioritynormalSeveritymajorReproducibilityalways
Status closedResolutionfixed 
Platformx86_64OSRedHat EnterpriseOS Version5.2
Product Version1.2.0 
Target Version1.2.11Fixed in Version1.2.11 
Summary0011661: "closed issue become readonly" doesn't work
Description

"closed issue become readonly" doesn't work

I tried to set NEXT STATUS to "empty" for CURRENT STATUS "closed" on Workflow (Workflow transitions), but I couldn't uncheck the checkbox (the check is still there)

On the other hand, if I set "Status where an issue becomes read only" to CLOSED, even it doesn't work (Workflow Thresholds)

So, reporters are able to reopen closed issues.
I want that reporters can only reopen resolved issues.

Tagsstatus

Relationships

related to 0011502 closeddhx No Close button for Reporter if allow_reporter_close is enabled 
related to 0012129 closeddregad workflow transition to status reopened is always checked for some status on workflow transition page 
related to 0015721 closedgrangeway Functionality to consider porting to master-2.0.x 
has duplicate 0011899 closeddhx readonly closed issues can be reopened 
related to 0014156 closeddregad Add Close button for Reporter if allow_reporter_close is enabled 

Activities

llattan

llattan

2010-03-21 22:59

reporter   ~0024835

Did anybody experience this error ?

llattan

llattan

2010-03-22 20:55

reporter   ~0024854

I can't upgrade my production system to 1.2.0 if I get this error.

I think this issue has major severity.

Let me know if I'm wrong.

llattan

llattan

2010-03-28 21:28

reporter   ~0024915

Has anybody experienced this error ?

llattan

llattan

2010-04-02 21:00

reporter   ~0025004

Victor, could you help me ?
Is it a bug ?

llattan

llattan

2010-05-02 23:40

reporter   ~0025366

dhx, could you help me ?
Is it a bug ?

llattan

llattan

2010-10-05 08:29

reporter   ~0026953

"Status where an issue becomes read only" (CLOSED) must be stronger than
"Allow Reporter to re-open Issue"

So, REPORTER (or NOBODY / or configurable access level) could reopen a READ ONLY issue.

caldarola

caldarola

2010-11-19 10:17

reporter   ~0027427

Last edited: 2010-11-19 10:21

I got the same error (1.2.2)

caldarola

caldarola

2010-11-19 10:22

reporter   ~0027428

I was wrong, with 1.2.2 I didn't get this issue.

ceedreva

ceedreva

2011-04-18 15:03

reporter   ~0028650

very good

kelson

kelson

2012-02-15 05:06

reporter   ~0031242

What does "read-only" really mean ?

In 1.2.5 version, when a bug becomes "resolved", according to the workflow, the bug is read-only and only manager can edit it.
When someone with right under manager is logged, the button "edit" disappears but he still can change the status.

Is there a way to forbid to change the status of read-only bug ?

gthomas

gthomas

2012-04-03 01:41

reporter   ~0031590

Hi kelson!

I've met with this, and I had to modify core/print_api.php:

diff --git a/core/print_api.php b/core/print_api.php
index a8a9fff..12f89ac 100644
--- a/core/print_api.php
+++ b/core/print_api.php
@@ -870,14 +870,14 @@ function get_status_option_list( $p_user_auth = 0, $p_current_value = 0, $p_show

    if( count( $t_enum_workflow ) < 1 ) {
            # workflow not defined, use default enum
  • $t_enum_values = MantisEnum::getValues( $t_config_var_value );
  • $t_enum_values = array( $p_current_value );
    } else {

    workflow defined - find allowed states

            if( isset( $t_enum_workflow[$p_current_value] ) ) {
                    $t_enum_values = MantisEnum::getValues( $t_enum_workflow[$p_current_value] );
            } else {
                    # workflow was not set for this status, this shouldn't happen
  • $t_enum_values = MantisEnum::getValues( $t_config_var_value );
  • $t_enum_values = array( $p_current_value );
    }
    }

If there is no states to transit to, then all states are displayed!
My modification changes this to show just the current state in this case.

GThomas

dregad

dregad

2012-04-04 07:59

developer   ~0031595

There is indeed a problem with the "Change status to" button+list, which does not respect the workflow settings.

Eg. even with "Reopen issue" allowed only for Admin and "Allow reporter to re-open" unchecked, a reporter is still able to change issue status to "feedback".

The "Move" button also does not respect the "readonly" threshold.

dregad

dregad

2012-04-04 11:17

developer   ~0031596

Refering to the original issue description "but I couldn't uncheck the checkbox (the check is still there)" - this is actually another issue, and only related to the display of the workflow the values are stored correctly - see 0012129

dregad

dregad

2012-04-14 19:44

developer   ~0031655

I committed some changes today (see 0014156) which I think should address this issue also, so I'm marking it as resolved.

Feel free to reopen with comments should the problem persist.

grangeway

grangeway

2013-04-05 17:57

reporter   ~0036253

Marking as 'acknowledged' not resolved/closed to track that change gets ported to master-2.0.x branch