Defect #9966
Private issue permissions
Status: | Resolved | Start date: | 2012-01-10 | |
---|---|---|---|---|
Priority: | Normal | Due date: | ||
Assignee: | - | % Done: | 0% | |
Category: | Issues permissions | |||
Target version: | - | |||
Resolution: | Affected version: | 1.3.0 |
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)
History
#1
Updated by Lu Pon over 2 years ago
- Status changed from New to Resolved