View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0011661 | mantisbt | administration | public | 2010-03-15 18:09 | 2014-09-23 18:05 |
Reporter | llattan | Assigned To | dregad | ||
Priority | normal | Severity | major | Reproducibility | always |
Status | closed | Resolution | fixed | ||
Platform | x86_64 | OS | RedHat Enterprise | OS Version | 5.2 |
Product Version | 1.2.0 | ||||
Target Version | 1.2.11 | Fixed in Version | 1.2.11 | ||
Summary | 0011661: "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. | ||||
Tags | status | ||||
related to | 0011502 | closed | dhx | No Close button for Reporter if allow_reporter_close is enabled |
related to | 0012129 | closed | dregad | workflow transition to status reopened is always checked for some status on workflow transition page |
related to | 0015721 | closed | grangeway | Functionality to consider porting to master-2.0.x |
has duplicate | 0011899 | closed | dhx | readonly closed issues can be reopened |
related to | 0014156 | closed | dregad | Add Close button for Reporter if allow_reporter_close is enabled |
Did anybody experience this error ? |
|
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. |
|
Has anybody experienced this error ? |
|
Victor, could you help me ? |
|
dhx, could you help me ? |
|
"Status where an issue becomes read only" (CLOSED) must be stronger than So, REPORTER (or NOBODY / or configurable access level) could reopen a READ ONLY issue. |
|
I got the same error (1.2.2) |
|
I was wrong, with 1.2.2 I didn't get this issue. |
|
very good |
|
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. Is there a way to forbid to change the status of read-only bug ? |
|
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
If there is no states to transit to, then all states are displayed! GThomas |
|
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. |
|
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 |
|
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. |
|
Marking as 'acknowledged' not resolved/closed to track that change gets ported to master-2.0.x branch |
|