MantisBT
Main | My View | View Issues | Change Log | Roadmap | Wiki | ManTweet | Repositories
  

View Issue Details [ Jump to Notes ] [ Wiki ] [ Issue History ] [ Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0011661mantisbtadministrationpublic2010-03-15 18:092013-04-06 09:23
Reporterllattan 
Assigned Todregad 
PrioritynormalSeveritymajorReproducibilityalways
StatusclosedResolutionfixed 
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.
Tags2.0.x check, status
Attached Files

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

-  Notes
User avatar (0024835)
llattan (reporter)
2010-03-21 22:59

 Did anybody experience this error ?
User avatar (0024854)
llattan (reporter)
2010-03-22 20:55

 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.
User avatar (0024915)
llattan (reporter)
2010-03-28 21:28

 Has anybody experienced this error ?
User avatar (0025004)
llattan (reporter)
2010-04-02 21:00

 Victor, could you help me ?
Is it a bug ?
User avatar (0025366)
llattan (reporter)
2010-05-02 23:40

 dhx, could you help me ?
Is it a bug ?
User avatar (0026953)
llattan (reporter)
2010-10-05 08:29

 "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.
User avatar (0027427)
caldarola (reporter)
2010-11-19 10:17
edited on: 2010-11-19 10:21

 I got the same error (1.2.2)
User avatar (0027428)
caldarola (reporter)
2010-11-19 10:22

 I was wrong, with 1.2.2 I didn't get this issue.
User avatar (0028650)
ceedreva (reporter)
2011-04-18 15:03

 very good
User avatar (0031242)
kelson (reporter)
2012-02-15 05:06

 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 ?
User avatar (0031590)
gthomas (reporter)
2012-04-03 01:41

 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
User avatar (0031595)
dregad (developer)
2012-04-04 07:59

 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.
User avatar (0031596)
dregad (developer)
2012-04-04 11:17

 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
User avatar (0031655)
dregad (developer)
2012-04-14 19:44

 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.
User avatar (0036253)
grangeway (developer)
2013-04-05 17:57

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

- Issue History
Date Modified Username Field Change
2010-03-15 18:09 llattan New Issue
2010-03-21 22:59 llattan Note Added: 0024835
2010-03-22 20:55 llattan Note Added: 0024854
2010-03-28 21:28 llattan Note Added: 0024915
2010-04-02 21:00 llattan Note Added: 0025004
2010-05-02 23:37 llattan Tag Attached: status
2010-05-02 23:40 llattan Note Added: 0025366
2010-05-10 12:40 dhx Relationship added has duplicate 0011899
2010-05-10 12:41 dhx Target Version => 1.2.2
2010-07-29 10:41 jreese Target Version 1.2.2 => 1.2.3
2010-09-14 10:55 jreese Target Version 1.2.3 => 1.2.4
2010-10-05 08:29 llattan Note Added: 0026953
2010-11-19 10:17 caldarola Note Added: 0027427
2010-11-19 10:21 caldarola Note Edited: 0027427 View Revisions
2010-11-19 10:21 caldarola Note Edited: 0027427 View Revisions
2010-11-19 10:22 caldarola Note Added: 0027428
2010-12-14 21:05 jreese Target Version 1.2.4 => 1.2.5
2011-04-05 12:25 jreese Target Version 1.2.5 => 1.2.6
2011-04-18 15:03 ceedreva Note Added: 0028650
2011-07-26 09:53 jreese Target Version 1.2.6 => 1.2.7
2011-08-22 10:49 jreese Target Version 1.2.7 => 1.2.8
2011-09-06 10:33 jreese Target Version 1.2.8 => 1.2.9
2012-02-15 05:06 kelson Note Added: 0031242
2012-03-04 09:23 atrol Target Version 1.2.9 => 1.2.10
2012-04-02 02:33 atrol Target Version 1.2.10 => 1.2.11
2012-04-03 01:41 gthomas Note Added: 0031590
2012-04-04 07:59 dregad Note Added: 0031595
2012-04-04 07:59 dregad Assigned To => dregad
2012-04-04 07:59 dregad Status new => confirmed
2012-04-04 08:00 dregad Relationship added related to 0011502
2012-04-04 11:17 dregad Note Added: 0031596
2012-04-04 11:17 dregad Relationship added related to 0012129
2012-04-14 19:42 dregad Relationship added related to 0014156
2012-04-14 19:44 dregad Note Added: 0031655
2012-04-14 19:44 dregad Status confirmed => resolved
2012-04-14 19:44 dregad Fixed in Version => 1.2.11
2012-04-14 19:44 dregad Resolution open => fixed
2012-06-06 23:53 jreese Status resolved => closed
2013-04-05 17:57 grangeway Status closed => acknowledged
2013-04-05 17:57 grangeway Note Added: 0036253
2013-04-05 18:36 grangeway Relationship added related to 0015721
2013-04-06 03:40 dregad Status acknowledged => closed
2013-04-06 07:23 grangeway Status closed => acknowledged
2013-04-06 09:22 dregad Tag Attached: 2.0.x check
2013-04-06 09:23 dregad Status acknowledged => closed

MantisBT 1.2.16dev master-1.2.x-8c2bd07 [^]
Copyright © 2000 - 2013 MantisBT Team
Time: 0.1079 seconds.
memory usage: 2,927 KB
Powered by Mantis Bugtracker