Actions
Defect #9966
openPrivate issue permissions
Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
Issues permissions
Target version:
-
Start date:
2012-01-10
Due date:
% Done:
0%
Estimated time:
Resolution:
Affected version:
Description
Hi, in 1.3.0, we realize that "private issue" has a different behavior.
When I put an issue as "private" on a public project, that issue can only be accessed by myself. I mean, I have coordinator privileges, I change public/private to issue and then a developer can't see that issue.
I had checked permissions at "Administration" and searched all issues here in Redmine's site without luck.
Is it a new behavior or is a bug?
Information about my environment:
mysql Ver 14.14 Distrib 5.1.41 -- Ruby version 1.8.7 (x86_64-linux) RubyGems version 1.3.7 Rack version 1.1.2 Rails version 2.3.14 Database schema version 20110902000000 -- Redmine 1.3.0.stable.8325
thanks !
(apologies about my english)
Actions