https://www.redmine.org/https://www.redmine.org/favicon.ico?16793021292009-02-27T15:08:54ZRedmineRedmine - Feature #2653: New permission for issues: view_own_issuehttps://www.redmine.org/issues/2653?journal_id=77052009-02-27T15:08:54ZJean-Philippe Langjp_lang@yahoo.fr
<ul><li><strong>Category</strong> changed from <i>Permissions and roles</i> to <i>Issues permissions</i></li></ul> Redmine - Feature #2653: New permission for issues: view_own_issuehttps://www.redmine.org/issues/2653?journal_id=100352009-07-04T19:08:07ZMaik Derstappen
<ul></ul><p>+1</p> Redmine - Feature #2653: New permission for issues: view_own_issuehttps://www.redmine.org/issues/2653?journal_id=100382009-07-05T09:03:14ZJan from Planio www.plan.io
<ul></ul><p>+1</p> Redmine - Feature #2653: New permission for issues: view_own_issuehttps://www.redmine.org/issues/2653?journal_id=103272009-07-24T10:15:17ZHolger Winkelmann
<ul></ul><p>+1</p> Redmine - Feature #2653: New permission for issues: view_own_issuehttps://www.redmine.org/issues/2653?journal_id=103362009-07-25T00:19:38ZEnderson Maia
<ul></ul><p>+1</p> Redmine - Feature #2653: New permission for issues: view_own_issuehttps://www.redmine.org/issues/2653?journal_id=103882009-07-28T21:17:14ZThomas Pihl
<ul></ul><p>See <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: "View Issues" user permission (Closed)" href="https://www.redmine.org/issues/3187">#3187</a></p> Redmine - Feature #2653: New permission for issues: view_own_issuehttps://www.redmine.org/issues/2653?journal_id=103902009-07-28T21:24:43ZDmitry Shkolnikov
<ul></ul><p>+1</p> Redmine - Feature #2653: New permission for issues: view_own_issuehttps://www.redmine.org/issues/2653?journal_id=109862009-09-15T09:07:56ZJ Cayetano Delgado
<ul></ul><p>+1</p> Redmine - Feature #2653: New permission for issues: view_own_issuehttps://www.redmine.org/issues/2653?journal_id=121522009-11-17T10:29:40ZTiago Queirós
<ul></ul><p>+1</p> Redmine - Feature #2653: New permission for issues: view_own_issuehttps://www.redmine.org/issues/2653?journal_id=121662009-11-17T19:52:36ZStanislav German-Evtushenko
<ul></ul><p>I think it would be great if it will be implemented in 0.9 in addition to Private issues <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: Private issues (Closed)" href="https://www.redmine.org/issues/337">#337</a>.</p> Redmine - Feature #2653: New permission for issues: view_own_issuehttps://www.redmine.org/issues/2653?journal_id=124852009-11-27T03:22:53ZHo Nguyen
<ul></ul><p>+1</p> Redmine - Feature #2653: New permission for issues: view_own_issuehttps://www.redmine.org/issues/2653?journal_id=124862009-11-27T06:48:36ZLucas Panjer
<ul></ul><p>+1</p> Redmine - Feature #2653: New permission for issues: view_own_issuehttps://www.redmine.org/issues/2653?journal_id=126262009-12-02T16:55:47ZStanislav German-Evtushenko
<ul></ul><p>It seems as resolved here in issue <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: "View Issues" user permission (Closed)" href="https://www.redmine.org/issues/3187">#3187</a>!</p> Redmine - Feature #2653: New permission for issues: view_own_issuehttps://www.redmine.org/issues/2653?journal_id=126332009-12-02T18:00:33ZStanislav German-Evtushenko
<ul></ul><p>Stanislav German-Evtushenko wrote:</p>
<blockquote>
<p>It seems as resolved here in issue <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: "View Issues" user permission (Closed)" href="https://www.redmine.org/issues/3187">#3187</a>!</p>
</blockquote>
<p>No :(<br />Isn't implemented yet</p> Redmine - Feature #2653: New permission for issues: view_own_issuehttps://www.redmine.org/issues/2653?journal_id=127752009-12-07T12:34:51ZChristophe Le Guern
<ul></ul><p>+1</p> Redmine - Feature #2653: New permission for issues: view_own_issuehttps://www.redmine.org/issues/2653?journal_id=132222009-12-23T20:19:20ZStanislav German-Evtushenko
<ul><li><strong>Assignee</strong> set to <i>Jean-Philippe Lang</i></li></ul><p>Hello Jean-Philippe,</p>
<p>Could it be implemented in 0.9 version?</p> Redmine - Feature #2653: New permission for issues: view_own_issuehttps://www.redmine.org/issues/2653?journal_id=144402010-02-17T14:49:59ZAlexander Stehlik
<ul></ul><p>+1</p> Redmine - Feature #2653: New permission for issues: view_own_issuehttps://www.redmine.org/issues/2653?journal_id=159712010-04-18T16:21:43ZThomas Pihl
<ul></ul><p>+1 (would be really great)</p> Redmine - Feature #2653: New permission for issues: view_own_issuehttps://www.redmine.org/issues/2653?journal_id=161362010-04-24T05:13:34ZOleg Volkov
<ul></ul><p>What is different from <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: Private issues (Closed)" href="https://www.redmine.org/issues/337">#337</a> ?<br /><a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: Private issues (Closed)" href="https://www.redmine.org/issues/337">#337</a> is already working<br />For external users (Not member):<br />- set "View issue" <br />- unset "Add issue" <br />- set "Add private issue" <br />- unset "View private issue" <br />For internal users (Developer, Manager):<br />- set "View issue" <br />- set or unset "Add issue" <br />- set or unset "Add private issue" <br />- set "View private issue"</p> Redmine - Feature #2653: New permission for issues: view_own_issuehttps://www.redmine.org/issues/2653?journal_id=161412010-04-25T09:35:57ZThomas Pihl
<ul></ul><p>The difference is that external users will see each others issues.</p>
<p>This is in alot of situations not desirable.</p>
<p>Currently we solve this with different projects per customer/user but would really like to make sure that each external user only see their own issues.</p> Redmine - Feature #2653: New permission for issues: view_own_issuehttps://www.redmine.org/issues/2653?journal_id=161422010-04-25T09:44:19ZOleg Volkov
<ul></ul><p>External users will NOT see each others PRIVATE issues.</p> Redmine - Feature #2653: New permission for issues: view_own_issuehttps://www.redmine.org/issues/2653?journal_id=161432010-04-25T09:49:02ZThomas Pihl
<ul></ul><p>True, but we don't want them to be able to enter anything that can be seen by other users, no matter how they mark it.</p>
<p>All their issues should be isolated from each others and support-center can work with them all.</p> Redmine - Feature #2653: New permission for issues: view_own_issuehttps://www.redmine.org/issues/2653?journal_id=161442010-04-25T09:51:24ZThomas Pihl
<ul></ul><p>I will read up on your <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: Private issues (Closed)" href="https://www.redmine.org/issues/337">#337</a> and do some tests.</p>
<p>You might be right or i need to formulate my ideas better.</p>
<p>BR,<br /> Thomas</p> Redmine - Feature #2653: New permission for issues: view_own_issuehttps://www.redmine.org/issues/2653?journal_id=161452010-04-25T10:00:04ZOleg Volkov
<ul></ul><p>External users (not member):<br />- not view other issues,<br />- view own issues</p>
<p>Developer users view all issues.</p>
<p>See <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: Private issues (Closed)" href="https://www.redmine.org/issues/337">#337</a> description and <a class="external" href="http://www.redmine.org/issues/2653#note-19">http://www.redmine.org/issues/2653#note-19</a></p> Redmine - Feature #2653: New permission for issues: view_own_issuehttps://www.redmine.org/issues/2653?journal_id=161462010-04-25T10:00:29ZStanislav German-Evtushenko
<ul></ul><p>Private issues looks like a little bit complex workaround for "view_own_issue".</p> Redmine - Feature #2653: New permission for issues: view_own_issuehttps://www.redmine.org/issues/2653?journal_id=161482010-04-25T10:12:29ZOleg Volkov
<ul></ul><p><a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: Private issues (Closed)" href="https://www.redmine.org/issues/337">#337</a> is able to work, please test it</p> Redmine - Feature #2653: New permission for issues: view_own_issuehttps://www.redmine.org/issues/2653?journal_id=161502010-04-25T11:43:21ZStanislav German-Evtushenko
<ul></ul><p>Oleg Volkov wrote:</p>
<blockquote>
<p><a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: Private issues (Closed)" href="https://www.redmine.org/issues/337">#337</a> is able to work, please test it</p>
</blockquote>
<p>I believe that it should work. Nevertheless it's really more than necessary. "View own issue" and "Create an issue" permissions would be enough I think.</p> Redmine - Feature #2653: New permission for issues: view_own_issuehttps://www.redmine.org/issues/2653?journal_id=161512010-04-25T11:55:30ZOleg Volkov
<ul></ul><p>Why?</p> Redmine - Feature #2653: New permission for issues: view_own_issuehttps://www.redmine.org/issues/2653?journal_id=161522010-04-25T12:12:45ZStanislav German-Evtushenko
<ul></ul><p>I'm not sure how can one use "Private tasks". You can use private project instead.<br />For example: I have two projects: IT Tasks (primary) and Helpdesk (child project).<br />Primary task is private - just only for IT team. Helpdesk - public project. And I think it would be nice if helpdesk users can see only their owned task and nothing else in the "helpdesk" project.</p> Redmine - Feature #2653: New permission for issues: view_own_issuehttps://www.redmine.org/issues/2653?journal_id=161532010-04-25T12:32:09ZOleg Volkov
<ul></ul><p>Set "Public" for Helpdesk project, unset "Public" for IT Tasks projects.<br />Unset "Add issue" for "Not member".<br />Set "Add private issue" for "Not member".<br />Set "View private issue" for "Developer" (for view all private issue).</p> Redmine - Feature #2653: New permission for issues: view_own_issuehttps://www.redmine.org/issues/2653?journal_id=161542010-04-25T12:42:22ZStanislav German-Evtushenko
<ul></ul><p>Oleg Volkov wrote:</p>
<blockquote>
<p>Set "Public" for Helpdesk project, unset "Public" for IT Tasks projects.<br />Unset "Add issue" for "Not member".<br />Set "Add private issue" for "Not member".<br />Set "View private issue" for "Developer" (for view all private issue).</p>
</blockquote>
<p>I got it, but I'm still not sure what the reason to do two types of issues (private and not private) when just only one enough?</p> Redmine - Feature #2653: New permission for issues: view_own_issuehttps://www.redmine.org/issues/2653?journal_id=161552010-04-25T12:43:04ZStanislav German-Evtushenko
<ul></ul><p>enough => is enough</p> Redmine - Feature #2653: New permission for issues: view_own_issuehttps://www.redmine.org/issues/2653?journal_id=161572010-04-25T13:31:57ZOleg Volkov
<ul></ul><p>Unset "Add issue" to all<br />Set "Add private issue" to all</p> Redmine - Feature #2653: New permission for issues: view_own_issuehttps://www.redmine.org/issues/2653?journal_id=161592010-04-25T15:14:06ZThomas Pihl
<ul></ul><p>It might be only terminology.</p>
<p>And i can see a point of being able to have both private and public issues in same project. Some helpdesk issues you may want to show to everyone but only after you first saw them (as private).</p>
<p>Also useful if you have a project with like a stearing group as guests. Some issues may be better hidden.</p>
<p>BR,<br /> Thomas</p> Redmine - Feature #2653: New permission for issues: view_own_issuehttps://www.redmine.org/issues/2653?journal_id=163522010-05-02T15:09:59ZOleg Volkov
<ul><li><strong>File</strong> <a href="/attachments/3667">redmine_own_v.1.patch</a> <a class="icon-only icon-download" title="Download" href="/attachments/download/3667/redmine_own_v.1.patch">redmine_own_v.1.patch</a> added</li></ul><p>This patch adds the ability to view own issues in the case if you have "Add issue" and not found "View issue". <br />Own issues are:<br />- created<br />- assigned<br />- watchers</p>
<p>Please test my patch and write reviews.</p> Redmine - Feature #2653: New permission for issues: view_own_issuehttps://www.redmine.org/issues/2653?journal_id=163932010-05-03T18:59:57ZSergey Belov
<ul></ul><p>This patch works fantastic. It's better that "private issue" patch because it works for old issues, and don't need to migrate db</p>
<p>Jean-Philippe, please take a look on this patch</p> Redmine - Feature #2653: New permission for issues: view_own_issuehttps://www.redmine.org/issues/2653?journal_id=163942010-05-03T20:20:15ZStanislav German-Evtushenko
<ul></ul><p>Thanks a lot, Oleg!<br />I'll try it on the 0.8-stable.</p> Redmine - Feature #2653: New permission for issues: view_own_issuehttps://www.redmine.org/issues/2653?journal_id=164052010-05-04T11:46:24ZStanislav German-Evtushenko
<ul></ul><p>I didn't manage to apply this patch for redmine 0.8 because there ara too much differences between 0.8 and 0.9 at the moment.</p>
<pre>
$ patch -p1 --dry-run < redmine_own_v.1.patch
patching file app/controllers/issues_controller.rb
Hunk #1 succeeded at 99 (offset -5 lines).
patching file app/models/issue.rb
Hunk #1 FAILED at 62.
1 out of 1 hunk FAILED -- saving rejects to file app/models/issue.rb.rej
patching file app/models/query.rb
Hunk #1 succeeded at 259 with fuzz 2 (offset -87 lines).
Hunk #2 succeeded at 281 (offset -87 lines).
Hunk #3 succeeded at 328 with fuzz 1 (offset -90 lines).
patching file app/models/user.rb
Hunk #1 FAILED at 289.
Hunk #2 FAILED at 297.
2 out of 2 hunks FAILED -- saving rejects to file app/models/user.rb.rej
patching file lib/redmine.rb
Hunk #1 succeeded at 18 with fuzz 2 (offset -7 lines).
Hunk #2 FAILED at 31.
Hunk #3 succeeded at 68 (offset -11 lines).
Hunk #4 succeeded at 89 (offset -11 lines).
1 out of 4 hunks FAILED -- saving rejects to file lib/redmine.rb.rej
patching file test/fixtures/issues.yml
Hunk #1 FAILED at 10.
Hunk #2 FAILED at 86.
Hunk #3 FAILED at 202.
3 out of 3 hunks FAILED -- saving rejects to file test/fixtures/issues.yml.rej
can't find file to patch at input line 201
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff -ur redmine-0.9.4/test/fixtures/member_roles.yml redmine/test/fixtures/member_roles.yml
|--- redmine-0.9.4/test/fixtures/member_roles.yml 2010-05-01 16:43:49.000000000 +0400
|+++ redmine/test/fixtures/member_roles.yml 2010-05-02 11:23:54.235688297 +0400
--------------------------
File to patch:
</pre> Redmine - Feature #2653: New permission for issues: view_own_issuehttps://www.redmine.org/issues/2653?journal_id=164192010-05-04T19:55:07ZOleg Volkov
<ul></ul><p>Patch for 0.9.4 and hi.</p> Redmine - Feature #2653: New permission for issues: view_own_issuehttps://www.redmine.org/issues/2653?journal_id=164552010-05-05T11:00:24ZRaghu Sunderam
<ul></ul><p>Hello Oleg</p>
<p>Thank you very much for implementing this long requested feature via a simple patch.</p>
<p>I have applied the patch in my installation of redmine v0.94.<br />The version is a stable one and not a snapshot.</p>
<p>I used the following command to apply the patch # patch -p1 < redmine_own_v.1.patch</p>
<p>I got the following as output</p>
<pre>
patching file app/controllers/issues_controller.rb
patching file app/models/issue.rb
patching file app/models/query.rb
patching file app/models/user.rb
patching file lib/redmine.rb
patching file test/fixtures/issues.yml
patching file test/fixtures/member_roles.yml
patching file test/fixtures/members.yml
patching file test/fixtures/roles.yml
patching file test/fixtures/users.yml
patching file test/fixtures/watchers.yml
patching file test/functional/issues_controller_test.rb
patching file test/unit/issue_test.rb
patching file test/unit/mailer_test.rb </pre>
<p>So i assumed the patch has been applied successfully.</p>
<p>I went to Roles and Permission and could not find any check box called "View Private Issues" or "Add Private Issue" or anything like that.</p>
<p>Please help me.</p> Redmine - Feature #2653: New permission for issues: view_own_issuehttps://www.redmine.org/issues/2653?journal_id=164742010-05-05T13:46:10ZStanislav German-Evtushenko
<ul></ul><p>This patch doesn't add any new permissions. It's only changes 'what to show' behaviour.<br />If you have just only 'Add issue' without 'View issue' permission you can see just only own created issues or if you are in watchers.</p> Redmine - Feature #2653: New permission for issues: view_own_issuehttps://www.redmine.org/issues/2653?journal_id=164802010-05-05T17:31:09ZOleg Volkov
<ul></ul><table>
<tr>
<td>Permission </td>
<td>Created issue </td>
<td>Assigned issue </td>
<td>Watching issue </td>
<td>Other issue </td>
</tr>
<tr>
<td>Unset "View issue" and unset "Add issue" </td>
<td>Not view </td>
<td>Not view </td>
<td>Not view </td>
<td>Not view </td>
</tr>
<tr>
<td>Unset "View issue" and set "Add issue" </td>
<td>View </td>
<td>View </td>
<td>View </td>
<td>Not view </td>
</tr>
<tr>
<td>Set "View issue" </td>
<td>View </td>
<td>View </td>
<td>View </td>
<td>View </td>
</tr>
</table> Redmine - Feature #2653: New permission for issues: view_own_issuehttps://www.redmine.org/issues/2653?journal_id=164832010-05-05T19:10:19ZOleg Volkov
<ul><li><strong>File</strong> <a href="/attachments/3698">redmine_own_v.2.patch</a> <a class="icon-only icon-download" title="Download" href="/attachments/download/3698/redmine_own_v.2.patch">redmine_own_v.2.patch</a> added</li></ul><p>In new version:<br />- Fixed work with attachments<br />- Minor changes</p> Redmine - Feature #2653: New permission for issues: view_own_issuehttps://www.redmine.org/issues/2653?journal_id=165052010-05-06T07:55:00ZRaghu Sunderam
<ul></ul><p>Hello Everybody</p>
<p>Thank you very much for your support.<br />I now have figured the way of working of this patch.</p> Redmine - Feature #2653: New permission for issues: view_own_issuehttps://www.redmine.org/issues/2653?journal_id=165712010-05-08T18:57:55ZThomas Pihl
<ul></ul><p>Can you see the issue if it's assigned to you?</p> Redmine - Feature #2653: New permission for issues: view_own_issuehttps://www.redmine.org/issues/2653?journal_id=166852010-05-12T20:14:00ZAlexander Neundorf
<ul></ul><p>+1</p>
<p>This is a really significant improvement for Redmine, and make it possible to use RedMine in many scenarious where it isn't a suitable solution today, because external users can either see everything or not even their own issues.<br />How are the chances that this goes into svn ?</p>
<p>Would be really cool :-)<br />Alex</p> Redmine - Feature #2653: New permission for issues: view_own_issuehttps://www.redmine.org/issues/2653?journal_id=168042010-05-16T17:59:52ZAndrew M-Y
<ul></ul><p>Applying the patch to v.0.9.4.devel.3739, there were some failures:</p>
<pre>
patching file lib/redmine.rb
Hunk #1 succeeded at 44 (offset 19 lines).
Hunk #2 FAILED at 57.
Hunk #3 FAILED at 93.
Hunk #4 succeeded at 121 (offset 21 lines).
2 out of 4 hunks FAILED -- saving rejects to file lib/redmine.rb.rej
patching file test/fixtures/issues.yml
Hunk #1 FAILED at 86.
Hunk #2 FAILED at 202.
2 out of 2 hunks FAILED -- saving rejects to file test/fixtures/issues.yml.rej
</pre> Redmine - Feature #2653: New permission for issues: view_own_issuehttps://www.redmine.org/issues/2653?journal_id=168112010-05-17T03:42:42ZOleg Volkov
<ul></ul><p>Use stable 0.9.4 version.</p> Redmine - Feature #2653: New permission for issues: view_own_issuehttps://www.redmine.org/issues/2653?journal_id=168472010-05-18T19:46:12Zyannick quenec'hdu
<ul></ul><p>+1</p>
<p>This function is very important to manage external user</p> Redmine - Feature #2653: New permission for issues: view_own_issuehttps://www.redmine.org/issues/2653?journal_id=168892010-05-20T09:09:03ZSweet Geng
<ul></ul><p>Hi ! i apply it to Redmine 0.9.2 stable <br />i find it works well at the begining, it really great.<br />but i find in "My Page", if user don't have "view issue" permission<br />he can see nothing in this page<br />is this problem the same in 0.9.4 or only in .2?</p> Redmine - Feature #2653: New permission for issues: view_own_issuehttps://www.redmine.org/issues/2653?journal_id=168912010-05-20T10:01:03ZOleg Volkov
<ul></ul><p>So conceived</p>
<p>The following patch allows viewing</p>
<pre>
--- a/app/models/issue.rb 2010-05-01 16:43:49.000000000 +0400
+++ b/app/models/issue.rb 2010-05-20 13:49:15.595862696 +0400
@@ -54,7 +54,8 @@
validates_numericality_of :estimated_hours, :allow_nil => true
named_scope :visible, lambda {|*args| { :include => :project,
- :conditions => Project.allowed_to_condition(args.first || User.current, :view_issues) } }
+ :conditions => Project.allowed_to_condition(args.first || User.current, :view_issues) +
+ ' or ' + Project.allowed_to_condition(args.first || User.current, :add_issues) } }
named_scope :open, :conditions => ["#{IssueStatus.table_name}.is_closed = ?", false], :include => :status
</pre> Redmine - Feature #2653: New permission for issues: view_own_issuehttps://www.redmine.org/issues/2653?journal_id=169342010-05-24T07:00:08ZSweet Geng
<ul></ul><p>Oleg Volkov wrote:</p>
<blockquote>
<p>So conceived</p>
<p>The following patch allows viewing</p>
<p>[...]</p>
</blockquote>
<p>OK got it<br />works well<br />thanks very much !</p> Redmine - Feature #2653: New permission for issues: view_own_issuehttps://www.redmine.org/issues/2653?journal_id=170102010-05-27T05:31:47ZSweet Geng
<ul></ul><p>Oleg Volkov wrote:</p>
<blockquote>
<p>So conceived</p>
<p>The following patch allows viewing</p>
<p>[...]</p>
</blockquote>
<p>Hi Oleg Volkov :</p>
<p>going to be perfect , but i find in "My Page" >> "watched issue" <br />i can also see the issues which already been "closed".<br />what can i do to not show that closed issues in "My Page"?</p>
<p>thanks very much</p> Redmine - Feature #2653: New permission for issues: view_own_issuehttps://www.redmine.org/issues/2653?journal_id=170392010-05-29T10:59:34ZOleg Volkov
<ul></ul><p>Sweet Geng wrote:</p>
<blockquote>
<p>going to be perfect , but i find in "My Page" >> "watched issue" <br />i can also see the issues which already been "closed".<br />what can i do to not show that closed issues in "My Page"?</p>
</blockquote>
<p>This does not apply to <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: New permission for issues: view_own_issue (Closed)" href="https://www.redmine.org/issues/2653">#2653</a></p> Redmine - Feature #2653: New permission for issues: view_own_issuehttps://www.redmine.org/issues/2653?journal_id=170532010-05-31T01:07:00ZSweet Geng
<ul></ul><p>Oleg Volkov wrote:</p>
<blockquote>
<p>Sweet Geng wrote:</p>
<blockquote>
<p>going to be perfect , but i find in "My Page" >> "watched issue" <br />i can also see the issues which already been "closed".<br />what can i do to not show that closed issues in "My Page"?</p>
</blockquote>
<p>This does not apply to <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: New permission for issues: view_own_issue (Closed)" href="https://www.redmine.org/issues/2653">#2653</a></p>
</blockquote>
<p>Yes, thanks very much</p> Redmine - Feature #2653: New permission for issues: view_own_issuehttps://www.redmine.org/issues/2653?journal_id=173862010-06-17T14:50:59ZEriks Dobelis
<ul></ul><p>+1</p>
<p>This is a very important one.<br />Can some target version be set on this?</p> Redmine - Feature #2653: New permission for issues: view_own_issuehttps://www.redmine.org/issues/2653?journal_id=174362010-06-19T03:24:27ZLight Kong
<ul></ul><p>+1</p> Redmine - Feature #2653: New permission for issues: view_own_issuehttps://www.redmine.org/issues/2653?journal_id=180302010-07-07T15:28:16ZDidi Baur
<ul></ul><p>Hi, great patch, exactly what I was looking for. Except, it doesn't appear to work for 0.9.5 stable (just setting "Add Issue" permission, nothing else - I can't see not even mine). Any chance you could update the patch to work with 0.9.5? Thanks a lot in advance!</p> Redmine - Feature #2653: New permission for issues: view_own_issuehttps://www.redmine.org/issues/2653?journal_id=180572010-07-08T09:31:38ZAnders Aagaard
<ul></ul><p>Great patch, you just saved me a lot of time making it myself :)</p> Redmine - Feature #2653: New permission for issues: view_own_issuehttps://www.redmine.org/issues/2653?journal_id=184102010-07-18T08:28:56ZWayne Walter
<ul></ul><p>Any way to control this per-project for non-members?</p>
<p>I ask because we have 2 projects that both have ability to receive incoming emails which create new user automatically and create new ticket.</p>
<p>These new users are treated at "non-members" for permissions on projects.</p>
<p>But Redmine only allows setting Add Issue or View Issue for Non-Members globally, right?</p>
<p>Unless you have another suggestion, my current idea is to add ability to incoming emails to auto-assign the user a chosen role on the project specified.</p>
<p>So this would be a new parameter for rdm-mailhandler.rb of --role</p>
<p>After doing this it would be possible to make incoming emails from new users automatically get reporter role on one project which has "View Issue" privilege but they only get Non-Member role on the other project which only has the "Add Issue" privilege.</p>
<p>Maybe this deserves separate ticket on Redmine.</p>
<p>Wayne</p> Redmine - Feature #2653: New permission for issues: view_own_issuehttps://www.redmine.org/issues/2653?journal_id=184952010-07-20T06:27:47ZOleg Volkov
<ul><li><strong>File</strong> <a href="/attachments/4147">redmine_own_v.2.patch</a> <a class="icon-only icon-download" title="Download" href="/attachments/download/4147/redmine_own_v.2.patch">redmine_own_v.2.patch</a> added</li></ul> Redmine - Feature #2653: New permission for issues: view_own_issuehttps://www.redmine.org/issues/2653?journal_id=188052010-07-29T12:28:34ZJoe Goloso
<ul></ul><p>Hello,</p>
<p>I'm running redmine "1.0.0 stable" and have applied the "redmine_own_v.2.patch" as described.</p>
<p>It looks like everything went ok (no errors in the process), but when I disable the "view_issues" permission for the "customer" role, users in this role are not able to see the "Issues" option in redmine main menu, so obviously, they can not see their "own/assigned/watched" issues, as expected.</p>
<p>Someone else having this problem?</p> Redmine - Feature #2653: New permission for issues: view_own_issuehttps://www.redmine.org/issues/2653?journal_id=188232010-07-29T17:40:27ZOleg Volkov
<ul></ul><p>Enable "Add_issues" for customer.</p> Redmine - Feature #2653: New permission for issues: view_own_issuehttps://www.redmine.org/issues/2653?journal_id=188492010-07-30T11:52:12ZJoe Goloso
<ul></ul><p>Thanks Oleg for your quick reply!</p>
<p>I've already enabled the "Add_issues" permission in "Roles » (Customer) » Permissions » Issue tracking » Add issues". If this option is not enabled, customers cannot see the option "New issue" in redmine top menu, so they can't report.</p>
<p>My problem is not Adding issues, but viewing the added issues later when the "View issues" permission is disabled in the "Customer" role.</p>
<p>If I understand how this patch works, I have to disable the "View Issues" permission in my "Customer" role in order for the customers to see only,</p>
<ul>
<li>Own reported issues (when the customer reports an issue, is able to see it)</li>
<li>Assigned issues (when the customer has an issue assigned, is able to see it)</li>
<li>Watched issues (when the customer is "watcher" for an issue, is able to see it)</li>
</ul>
<p>This is what I understand from your chart,</p>
<blockquote>
<table>
<tr>
<td>Permission </td>
<td>Created issue </td>
<td>Assigned issue </td>
<td>Watching issue </td>
<td>Other issue </td>
</tr>
<tr>
<td>Unset "View issue" and unset "Add issue" </td>
<td>Not view </td>
<td>Not view </td>
<td>Not view </td>
<td>Not view </td>
</tr>
<tr>
<td>Unset "View issue" and set "Add issue" </td>
<td>View </td>
<td>View </td>
<td>View </td>
<td>Not view </td>
</tr>
<tr>
<td>Set "View issue" </td>
<td>View </td>
<td>View </td>
<td>View </td>
<td>View </td>
</tr>
</table>
</blockquote>
<p>But when I unset "View issue" and set "Add issue", users with the "Customer" role can't see any issue.</p>
<p>What can I be doing wrong???</p>
<p>Thanks in advance!</p> Redmine - Feature #2653: New permission for issues: view_own_issuehttps://www.redmine.org/issues/2653?journal_id=188542010-07-30T16:57:11ZBruno Medeiros
<ul></ul><blockquote>
<p>What can I be doing wrong???</p>
</blockquote>
<p>I can't imagine, I've just installed a new instance of Redmine 1.0.0 and applied the patch and everything works ok. My intention here is to use redmine to manage administrative demands, so the request from one employee can't be showed to other employees. I put on 'Non member' role the following permissions, separeted by groups:</p>
<p>Post messages</p>
<p>View documents</p>
<p>View files</p>
<p>Add issues <br />Edit issues <br />Add notes</p>
<p>View wiki</p>
<p>It's working fine, just as the table above shows. I have other non-non-member role with the same permission and it's working too.</p>
<p>I guess something went wrong with tour installation.</p> Redmine - Feature #2653: New permission for issues: view_own_issuehttps://www.redmine.org/issues/2653?journal_id=188942010-08-02T16:04:12ZJoe Goloso
<ul></ul><p>Ok. I'll install a new instance of redmine 1.0.0 and apply the patch. I'll give you feedback after the test.</p>
<p>Thanks again for your excelent work and support!</p> Redmine - Feature #2653: New permission for issues: view_own_issuehttps://www.redmine.org/issues/2653?journal_id=189622010-08-04T14:57:03Zanisa s.
<ul></ul><p>Hi,</p>
<p>I am also using the latest version of redmine (vs.1.0.0) and I was not able to install the patch. I got the following messages:<br /><pre>
File to patch: redmine_own_v.2.patch
patching file redmine_own_v.2.patch
Hunk #1 FAILED at 111.
1 out of 1 hunk FAILED -- saving rejects to file redmine_own_v.2.patch.rej
can't find file to patch at input line 16
Perhaps you used the wrong -p or --strip option?
</pre></p>
<p>Additionally the file redmine_own:v.2patch.rej has the following:<br /><pre>
--- redmine-1.0.0/app/controllers/issues_controller.rb 2010-06-05 07:52:59.000000000 +0400
+++ redmine/app/controllers/issues_controller.rb 2010-07-19 19:52:43.152810115 +0400
@@ -111,6 +111,7 @@
end
def show
+ return render_403 if !@issue.visible?
@journals = @issue.journals.find(:all, :include => [:user, :details], :order => "#{Journal.table_name}.created_on ASC")
@journals.each_with_index {|j,i| j.indice = i+1}
@journals.reverse! if User.current.wants_comments_in_reverse_order?
</pre></p>
<p>I would really appreciate your help on this issue.</p>
<p>Thnx in advance!</p> Redmine - Feature #2653: New permission for issues: view_own_issuehttps://www.redmine.org/issues/2653?journal_id=189632010-08-04T15:12:40ZBruno Medeiros
<ul></ul><p>To apply the patch you need to do the following:</p>
<pre>
[bruno.medeiros@appserver ~]$ cd /to/your/redmine/current/
[bruno.medeiros@appserver current]$ ls
app backup config db doc extra files lib log public Rakefile README.rdoc script test tmp vendor
[bruno.medeiros@appserver current]$ sudo wget http://www.redmine.org/attachments/download/4147/redmine_own_v.2.patch
[bruno.medeiros@appserver current]$ sudo patch -p1 < redmine_own_v.2.patch
</pre>
<p>I guess you problem is you didn't put the -p correctly, as said on the patch error:<br /><pre>
Perhaps you used the wrong -p or --strip option?
</pre></p> Redmine - Feature #2653: New permission for issues: view_own_issuehttps://www.redmine.org/issues/2653?journal_id=189652010-08-04T16:07:27Zanisa s.
<ul></ul><p>I actually tried both option "-p" and "--strip" but it did not work.<br />I followed your instructions and it worked. Before I was using the instructions described on this link <a class="external" href="http://www.redmine.org/wiki/redmine/patch">http://www.redmine.org/wiki/redmine/patch</a>.</p>
<p>Thnx a lot!</p>
<p>p.s: You also see the issues posted by other members but you cannot read them right?</p> Redmine - Feature #2653: New permission for issues: view_own_issuehttps://www.redmine.org/issues/2653?journal_id=189672010-08-04T17:03:33ZBruno Medeiros
<ul></ul><p>You don't even see the issues.</p>
<p>I recommend you to do some experiments with fake users and issues to see if this patch does what you really want.</p> Redmine - Feature #2653: New permission for issues: view_own_issuehttps://www.redmine.org/issues/2653?journal_id=189682010-08-04T17:14:05ZBruno Medeiros
<ul></ul><p>anisa s. wrote:</p>
<blockquote>
<p>I actually tried both option "-p" and "--strip" but it did not work.<br />I followed your instructions and it worked. Before I was using the instructions described on this link <a class="external" href="http://www.redmine.org/wiki/redmine/patch">http://www.redmine.org/wiki/redmine/patch</a>.</p>
</blockquote>
<p>Yeah, I tried that before too, but Oleg is not creating patches inside Redmine folder as said in this wiki, but one level up. So the <code>-p1</code> parameters says to patch to ignore the first folder on the hunks.</p> Redmine - Feature #2653: New permission for issues: view_own_issuehttps://www.redmine.org/issues/2653?journal_id=197642010-08-26T02:05:37ZBruno Medeiros
<ul></ul><p>I could do a 'svn update' on the 1.0-stable branch and all went fine, no conflicts. I tested the basics and doesn't seems to have permission issues. Has anyone else tried to update?</p> Redmine - Feature #2653: New permission for issues: view_own_issuehttps://www.redmine.org/issues/2653?journal_id=202412010-09-13T16:47:47ZEric Davis
<ul><li><strong>Assignee</strong> changed from <i>Jean-Philippe Lang</i> to <i>Eric Davis</i></li></ul><p>Assigning this to myself so I remember to review it once I'm done with a book launch.</p> Redmine - Feature #2653: New permission for issues: view_own_issuehttps://www.redmine.org/issues/2653?journal_id=202422010-09-13T16:52:22ZOleg Volkov
<ul><li><strong>File</strong> <a href="/attachments/4462">redmine_own_v.2.patch</a> <a class="icon-only icon-download" title="Download" href="/attachments/download/4462/redmine_own_v.2.patch">redmine_own_v.2.patch</a> added</li></ul> Redmine - Feature #2653: New permission for issues: view_own_issuehttps://www.redmine.org/issues/2653?journal_id=205562010-09-21T00:46:56ZSteven Hajducko
<ul></ul><p>Tried redmine_own_v.2.patch with a test user on 1.0-stable branch.</p>
<p>Test user has 'Add Issue' permission set, 'View Issue' permission unset. Test user is able to see issue list, but cannot read any issue details.</p> Redmine - Feature #2653: New permission for issues: view_own_issuehttps://www.redmine.org/issues/2653?journal_id=205582010-09-21T01:24:04ZSteven Hajducko
<ul></ul><p>Steven Hajducko wrote:</p>
<blockquote>
<p>Tried redmine_own_v.2.patch with a test user on 1.0-stable branch.</p>
<p>Test user has 'Add Issue' permission set, 'View Issue' permission unset. Test user is able to see issue list, but cannot read any issue details.</p>
</blockquote>
<p>Figured out the issue. Test User was actually created with a new role 'Test' that was assigned to the project. The special 'Non-member' role still had 'View Issues' available. Once the 'Non-member' role ( which the Test user is NOT a part of ) had it's 'View Issue' permission revoked, the patch worked.</p>
<p>So the patch <strong>requires</strong> that the Non-member role not be allowed to view <strong>any</strong> issues other than issues on those projects a non-member can create issues on, as a task cannot be assigned to a non-member and in order to watch an issue, a non-member would have to be able see the issue first.</p>
<p>Unfortunately, this makes it rather hard for us, as we use the non-member role for people who would like to comment on issues as well as other trivial things. There are specific, targeted people who we would like to restrict their view of the tasks on the project without having to disable the ability of non-members to view issues.</p> Redmine - Feature #2653: New permission for issues: view_own_issuehttps://www.redmine.org/issues/2653?journal_id=205602010-09-21T07:27:55ZOleg Volkov
<ul></ul><p>Inheriting privileges from the "no member" is a property redmine, and not the property of the patch 2653.</p> Redmine - Feature #2653: New permission for issues: view_own_issuehttps://www.redmine.org/issues/2653?journal_id=210802010-10-07T01:48:09ZAbhimanyu Grover
<ul></ul><p>Joe Goloso wrote:</p>
<blockquote>
<p>Thanks Oleg for your quick reply!</p>
<p>I've already enabled the "Add_issues" permission in "Roles » (Customer) » Permissions » Issue tracking » Add issues". If this option is not enabled, customers cannot see the option "New issue" in redmine top menu, so they can't report.</p>
<p>My problem is not Adding issues, but viewing the added issues later when the "View issues" permission is disabled in the "Customer" role.</p>
<p>If I understand how this patch works, I have to disable the "View Issues" permission in my "Customer" role in order for the customers to see only,</p>
<ul>
<li>Own reported issues (when the customer reports an issue, is able to see it)</li>
<li>Assigned issues (when the customer has an issue assigned, is able to see it)</li>
<li>Watched issues (when the customer is "watcher" for an issue, is able to see it)</li>
</ul>
<p>This is what I understand from your chart,</p>
<blockquote>
<table>
<tr>
<td>Permission </td>
<td>Created issue </td>
<td>Assigned issue </td>
<td>Watching issue </td>
<td>Other issue </td>
</tr>
<tr>
<td>Unset "View issue" and unset "Add issue" </td>
<td>Not view </td>
<td>Not view </td>
<td>Not view </td>
<td>Not view </td>
</tr>
<tr>
<td>Unset "View issue" and set "Add issue" </td>
<td>View </td>
<td>View </td>
<td>View </td>
<td>Not view </td>
</tr>
<tr>
<td>Set "View issue" </td>
<td>View </td>
<td>View </td>
<td>View </td>
<td>View </td>
</tr>
</table>
</blockquote>
<p>But when I unset "View issue" and set "Add issue", users with the "Customer" role can't see any issue.</p>
<p>What can I be doing wrong???</p>
<p>Thanks in advance!</p>
</blockquote>
<p>I'm having this exact same issue. Anyone else?</p> Redmine - Feature #2653: New permission for issues: view_own_issuehttps://www.redmine.org/issues/2653?journal_id=210932010-10-07T06:37:37ZOleg Volkov
<ul></ul><p>Too little information to understand the reason. Are you sure that the patch is installed correctly?<br />We present a scheme permissions.</p> Redmine - Feature #2653: New permission for issues: view_own_issuehttps://www.redmine.org/issues/2653?journal_id=211232010-10-07T19:26:10ZDiego Felipe
<ul></ul><p>Any plans to include this in the main branch?<br />Does It work with redmine v. 1.0.2? <br />I am using the 1.0.1 version, but the new gant features got my attention.</p>
<p>Thanks a lot Oleg.</p> Redmine - Feature #2653: New permission for issues: view_own_issuehttps://www.redmine.org/issues/2653?journal_id=211242010-10-07T19:56:16ZTerence Mill
<ul></ul><p>+1</p> Redmine - Feature #2653: New permission for issues: view_own_issuehttps://www.redmine.org/issues/2653?journal_id=211782010-10-08T19:48:20ZOleg Volkov
<ul><li><strong>File</strong> <a href="/attachments/4642">redmine_own_v.2.patch</a> <a class="icon-only icon-download" title="Download" href="/attachments/download/4642/redmine_own_v.2.patch">redmine_own_v.2.patch</a> added</li></ul><p>For redmine 1.0.2</p> Redmine - Feature #2653: New permission for issues: view_own_issuehttps://www.redmine.org/issues/2653?journal_id=211942010-10-10T11:56:29ZJoe Goloso
<ul></ul><p>Abhimanyu Grover wrote:</p>
<blockquote>
<p>I'm having this exact same issue. Anyone else?</p>
</blockquote>
<p>Still not solved.</p>
<p>I've confirmed that in a new redmine installation the patch works perfectly, but with my data, it doesn't.</p>
<p>Suggestions are welcome.</p>
<p>Thanks!</p> Redmine - Feature #2653: New permission for issues: view_own_issuehttps://www.redmine.org/issues/2653?journal_id=211952010-10-10T12:18:32ZOleg Volkov
<ul></ul><p>Joe Goloso wrote:</p>
<blockquote>
<p>I've confirmed that in a new redmine installation the patch works perfectly, but with my data, it doesn't.</p>
</blockquote>
<p>Please give your details.</p> Redmine - Feature #2653: New permission for issues: view_own_issuehttps://www.redmine.org/issues/2653?journal_id=212472010-10-11T17:47:54ZJoe Goloso
<ul></ul><p>Oleg Volkov wrote:</p>
<blockquote>
<p>Please give your details.</p>
</blockquote>
<p>Hi Oleg,</p>
<p>We have spent the whole morning doing some tests, and finally we have found the problem.</p>
<p>Just reboot redmine after the installations of the patch "redmine_own_v.2.patch - For redmine 1.0.2 (16,4 KB) Oleg Volkov, 2010-10-08 21:48".</p>
<p>Here are the details of my newbie and sad story:</p>
<p>Our first test was to install a new/clean redmine 1.0.2 in a new server and apply the patch. The patch worked perfectly in this procedure. Users with "customer" role (which had "view issues" permission disabled),</p>
<pre><code>1 - Can see "Issues" option in the redmine main menu.<br /> 2 - Are able to see issues they have assigned/watched.<br /> 3 - Are not able to see issues they don't have assigned/watched.</code></pre>
<p>In production environment it didn't work. Users with "customer" role (with "view issues" permission disabled), were not able to see the "Issues" option in the redmine main menu after installing the patch. They couldn't access even their own reported issues.</p>
<p>Then we did a dump of the BBDD of the production server (where the patch didn't work) to the new and clean redmine with the patch working fine, and everything kept working fine. So, our data (projects, subprojects, roles, users, issues, etc.) is not causing the problem.</p>
<p>Then we thought that the problem could be caused by a plugin, so we cloned all the production environment (redmine files and directories, plugins, BBDD, etc.) to another server, in order to start a classic "try and error" procedure, uninstalling pluguins one by one. Once we finished uninstalling all the plugins, realize that the problem persisted.</p>
<p>Then we have tried to restart redmine and the ploblem has been solved. What a shame...</p>
<p>Abhimanyu, you need to install the last patch version "redmine_own_v.2.patch - For redmine 1.0.2 (16,4 KB) Oleg Volkov, 2010-10-08 21:48" if you are running redmine 1.0.2. This worked for us.</p>
<p>Hope this can help.</p>
<p>Thank you guys for your excellent work. Redmine is the best projects management system. I love it. And now I will be able to share it with the customers.</p> Redmine - Feature #2653: New permission for issues: view_own_issuehttps://www.redmine.org/issues/2653?journal_id=212592010-10-12T04:15:59ZOleg Volkov
<ul></ul><p>Joe Goloso wrote:</p>
<blockquote>
<p>Then we have tried to restart redmine and the ploblem has been solved.</p>
</blockquote>
<p>This property is Ruby on Rails. Restart needed.</p> Redmine - Feature #2653: New permission for issues: view_own_issuehttps://www.redmine.org/issues/2653?journal_id=213722010-10-14T03:16:37ZBruno Medeiros
<ul></ul><p>Just to let you all know, trying to do a 'svn update' from 1.0.1 to 1.0.2 does not work, unless you want to manually solve 2 conflicts in <code>lib/redmine.rb</code> (I did that, but I really didn't want to...).</p>
<p>I think the safest way to update is to 1.0.2 from 1.0.1 is doing a new checkout and applying the rebased patch.</p>
<p>BTW, how can I run the tests? I searched, but i found nothing.. So I tried:<br /><pre>
[root@appserver current]# rake test:engines:all
(in /opt/redmine_sup/1.0-stable)
rake aborted!
Access denied for user 'root'@'localhost' (using password: NO)
(See full trace by running task with --trace)
</pre><br />Thanks!</p> Redmine - Feature #2653: New permission for issues: view_own_issuehttps://www.redmine.org/issues/2653?journal_id=213752010-10-14T05:33:14ZOleg Volkov
<ul></ul><p>I make a patch for the official versions redmine.<br />Install the new version, then apply the patch.</p>
<p>The patch is being tested by developers, users do not need to run the tests.</p> Redmine - Feature #2653: New permission for issues: view_own_issuehttps://www.redmine.org/issues/2653?journal_id=213772010-10-14T08:15:58ZTerence Mill
<ul></ul><p>Can you make a plugin out of this or when will this be released to core?</p> Redmine - Feature #2653: New permission for issues: view_own_issuehttps://www.redmine.org/issues/2653?journal_id=213812010-10-14T09:55:44ZOleg Volkov
<ul></ul><p>Terence Mill wrote:</p>
<blockquote>
<p>Can you make a plugin out of this</p>
</blockquote>
<p>I will not make a plugin.</p>
<blockquote>
<p>or when will this be released to core?</p>
</blockquote>
<p>Eric Devis thinks about it.</p> Redmine - Feature #2653: New permission for issues: view_own_issuehttps://www.redmine.org/issues/2653?journal_id=217122010-10-25T14:58:58ZEric Davis
<ul><li><strong>Assignee</strong> deleted (<del><i>Eric Davis</i></del>)</li></ul> Redmine - Feature #2653: New permission for issues: view_own_issuehttps://www.redmine.org/issues/2653?journal_id=217942010-10-25T16:08:04ZOleg Volkov
<ul></ul><p>Patch is dead! :(</p> Redmine - Feature #2653: New permission for issues: view_own_issuehttps://www.redmine.org/issues/2653?journal_id=218352010-10-27T05:04:17Zou liu
<ul></ul><p>Is it possible for not showing view-own-issues only members in Overview/Member area? Also, is it possible not allowing those kind of members assign their issue? Because you may have an internal way to assign issue to an employee, and it's possible that later that employee just left.</p>
<p>Personally I like redmine a lot, but to use it as a ticketing system which talks to customer directly, there is still a long way to go, especially on security when there are multiple customers for a project. (for example, can we have files for one customer but not another, wiki entry? document? What if we want a customer/group to have multiple reporters so that they can see each other's issue but not another customer/group's issue)</p> Redmine - Feature #2653: New permission for issues: view_own_issuehttps://www.redmine.org/issues/2653?journal_id=218372010-10-27T05:21:31ZOleg Volkov
<ul></ul><p>Use subprojects for different groups</p> Redmine - Feature #2653: New permission for issues: view_own_issuehttps://www.redmine.org/issues/2653?journal_id=221772010-11-05T18:57:26ZArash Afrooze
<ul></ul><p>Hi oleg,<br />I tried to apply the patch to redmine 1.0.2 and got a bunch of failures. I'm not very good with redmine and patching in general. After applying the patch, my user can add issues and the 'View Issues' tab is also there, but they're unable to see the list of their own issues. I've only given them add issue access.</p>
<p>Here is the result or the patch:</p>
<p>patching file redmine/app/controllers/issues_controller.rb<br />Hunk <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Defect: permissions if not admin (Closed)" href="https://www.redmine.org/issues/1">#1</a> succeeded at 99 (offset 2 lines).<br />patching file redmine/app/models/issue.rb<br />Hunk <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Defect: permissions if not admin (Closed)" href="https://www.redmine.org/issues/1">#1</a> succeeded at 92 (offset 18 lines).<br />patching file redmine/app/models/query.rb<br />Hunk <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Defect: permissions if not admin (Closed)" href="https://www.redmine.org/issues/1">#1</a> succeeded at 385 (offset 6 lines).<br />Hunk <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Defect: Listing 5 projects on Welcome page (Closed)" href="https://www.redmine.org/issues/2">#2</a> FAILED at 407.<br />Hunk <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Defect: ajax pagination of projects (Closed)" href="https://www.redmine.org/issues/3">#3</a> FAILED at 457.<br />2 out of 3 hunks FAILED -- saving rejects to file redmine/app/models/query.rb.rej<br />patching file redmine/app/models/user.rb<br />Hunk <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Defect: permissions if not admin (Closed)" href="https://www.redmine.org/issues/1">#1</a> FAILED at 339.<br />Hunk <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Defect: Listing 5 projects on Welcome page (Closed)" href="https://www.redmine.org/issues/2">#2</a> FAILED at 347.<br />2 out of 2 hunks FAILED -- saving rejects to file redmine/app/models/user.rb.rej<br />patching file redmine/lib/redmine.rb<br />Hunk <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Defect: permissions if not admin (Closed)" href="https://www.redmine.org/issues/1">#1</a> succeeded at 45 (offset 1 line).<br />Hunk <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Defect: ajax pagination of projects (Closed)" href="https://www.redmine.org/issues/3">#3</a> FAILED at 94.<br />Hunk <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Defect: log problem (Closed)" href="https://www.redmine.org/issues/4">#4</a> succeeded at 122 (offset 1 line).<br />1 out of 4 hunks FAILED -- saving rejects to file redmine/lib/redmine.rb.rej<br />patching file redmine/test/fixtures/issues.yml<br />patching file redmine/test/fixtures/member_roles.yml<br />patching file redmine/test/fixtures/members.yml<br />patching file redmine/test/fixtures/roles.yml<br />patching file redmine/test/fixtures/users.yml<br />Hunk <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Defect: permissions if not admin (Closed)" href="https://www.redmine.org/issues/1">#1</a> succeeded at 152 with fuzz 2.<br />patching file redmine/test/fixtures/watchers.yml<br />patching file redmine/test/functional/issues_controller_test.rb<br />patching file redmine/test/unit/attachment_test.rb<br />patching file redmine/test/unit/issue_test.rb<br />Hunk <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Defect: Listing 5 projects on Welcome page (Closed)" href="https://www.redmine.org/issues/2">#2</a> succeeded at 752 (offset 52 lines).<br />patching file redmine/test/unit/mailer_test.rb<br />patching file redmine/vendor/plugins/acts_as_attachable/lib/acts_as_attachable.rb</p>
<p>Thanks a million</p> Redmine - Feature #2653: New permission for issues: view_own_issuehttps://www.redmine.org/issues/2653?journal_id=221782010-11-05T19:07:17ZOleg Volkov
<ul></ul><p>Arash Afrooze, You are wrong to apply the patch, mistakes should not be.</p> Redmine - Feature #2653: New permission for issues: view_own_issuehttps://www.redmine.org/issues/2653?journal_id=221802010-11-05T19:46:53ZStanislav German-Evtushenko
<ul></ul><p>I confirm. I just get the last stable version of redmine and applied the patch without any errors.<br /><pre>
$ svn co http://redmine.rubyforge.org/svn/branches/1.0-stable redmine-1.0
$ cd redmine-1.0
$ patch -p1 --dry-run -i ../redmine_own_v.2.patch
patching file app/controllers/issues_controller.rb
patching file app/models/issue.rb
patching file app/models/query.rb
patching file app/models/user.rb
patching file lib/redmine.rb
patching file test/fixtures/issues.yml
patching file test/fixtures/member_roles.yml
patching file test/fixtures/members.yml
patching file test/fixtures/roles.yml
patching file test/fixtures/users.yml
patching file test/fixtures/watchers.yml
patching file test/functional/issues_controller_test.rb
patching file test/unit/attachment_test.rb
patching file test/unit/issue_test.rb
Hunk #2 succeeded at 730 (offset 30 lines).
patching file test/unit/mailer_test.rb
patching file vendor/plugins/acts_as_attachable/lib/acts_as_attachable.rb
</pre></p> Redmine - Feature #2653: New permission for issues: view_own_issuehttps://www.redmine.org/issues/2653?journal_id=222762010-11-10T18:19:18ZDov Amihod
<ul></ul><p>Hi,</p>
<p>I am new to Redmine, and was looking for the feature exactly as Oleg has designed it. The problem is that applying the patch has failed for me as well. I'm using</p>
<p>Redmine 1.0.2.stable (MySQL)</p>
<p>and had errors similar to Arash. My installation is the default one from here</p>
<p><a class="external" href="http://www.turnkeylinux.org/redmine">http://www.turnkeylinux.org/redmine</a></p>
<p>Thanks.</p>
<p>Arash Afrooze wrote:</p>
<blockquote>
<p>Hi oleg,<br />I tried to apply the patch to redmine 1.0.2 and got a bunch of failures. I'm not very good with redmine and patching in general. After applying the patch, my user can add issues and the 'View Issues' tab is also there, but they're unable to see the list of their own issues. I've only given them add issue access.</p>
<p>Here is the result or the patch:</p>
<p>patching file redmine/app/controllers/issues_controller.rb<br />Hunk <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Defect: permissions if not admin (Closed)" href="https://www.redmine.org/issues/1">#1</a> succeeded at 99 (offset 2 lines).<br />patching file redmine/app/models/issue.rb<br />Hunk <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Defect: permissions if not admin (Closed)" href="https://www.redmine.org/issues/1">#1</a> succeeded at 92 (offset 18 lines).<br />patching file redmine/app/models/query.rb<br />Hunk <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Defect: permissions if not admin (Closed)" href="https://www.redmine.org/issues/1">#1</a> succeeded at 385 (offset 6 lines).<br />Hunk <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Defect: Listing 5 projects on Welcome page (Closed)" href="https://www.redmine.org/issues/2">#2</a> FAILED at 407.<br />Hunk <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Defect: ajax pagination of projects (Closed)" href="https://www.redmine.org/issues/3">#3</a> FAILED at 457.<br />2 out of 3 hunks FAILED -- saving rejects to file redmine/app/models/query.rb.rej<br />patching file redmine/app/models/user.rb<br />Hunk <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Defect: permissions if not admin (Closed)" href="https://www.redmine.org/issues/1">#1</a> FAILED at 339.<br />Hunk <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Defect: Listing 5 projects on Welcome page (Closed)" href="https://www.redmine.org/issues/2">#2</a> FAILED at 347.<br />2 out of 2 hunks FAILED -- saving rejects to file redmine/app/models/user.rb.rej<br />patching file redmine/lib/redmine.rb<br />Hunk <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Defect: permissions if not admin (Closed)" href="https://www.redmine.org/issues/1">#1</a> succeeded at 45 (offset 1 line).<br />Hunk <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Defect: ajax pagination of projects (Closed)" href="https://www.redmine.org/issues/3">#3</a> FAILED at 94.<br />Hunk <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Defect: log problem (Closed)" href="https://www.redmine.org/issues/4">#4</a> succeeded at 122 (offset 1 line).<br />1 out of 4 hunks FAILED -- saving rejects to file redmine/lib/redmine.rb.rej<br />patching file redmine/test/fixtures/issues.yml<br />patching file redmine/test/fixtures/member_roles.yml<br />patching file redmine/test/fixtures/members.yml<br />patching file redmine/test/fixtures/roles.yml<br />patching file redmine/test/fixtures/users.yml<br />Hunk <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Defect: permissions if not admin (Closed)" href="https://www.redmine.org/issues/1">#1</a> succeeded at 152 with fuzz 2.<br />patching file redmine/test/fixtures/watchers.yml<br />patching file redmine/test/functional/issues_controller_test.rb<br />patching file redmine/test/unit/attachment_test.rb<br />patching file redmine/test/unit/issue_test.rb<br />Hunk <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Defect: Listing 5 projects on Welcome page (Closed)" href="https://www.redmine.org/issues/2">#2</a> succeeded at 752 (offset 52 lines).<br />patching file redmine/test/unit/mailer_test.rb<br />patching file redmine/vendor/plugins/acts_as_attachable/lib/acts_as_attachable.rb</p>
<p>Thanks a million</p>
</blockquote> Redmine - Feature #2653: New permission for issues: view_own_issuehttps://www.redmine.org/issues/2653?journal_id=222772010-11-10T18:54:34ZOleg Volkov
<ul></ul><p>Use last patch for 1.0.2 and 1.0.3 version.</p>
<p>$ wget <a class="external" href="http://www.redmine.org/attachments/download/4642/redmine_own_v.2.patch">http://www.redmine.org/attachments/download/4642/redmine_own_v.2.patch</a><br />$ wget <a class="external" href="http://rubyforge.org/frs/download.php/73140/redmine-1.0.3.tar.gz">http://rubyforge.org/frs/download.php/73140/redmine-1.0.3.tar.gz</a><br />$ tar -zxvf redmine-1.0.3.tar.gz<br />$ cd redmine-1.0.3<br />$ patch -p 1 ../redmine_own_v.2.patch</p> Redmine - Feature #2653: New permission for issues: view_own_issuehttps://www.redmine.org/issues/2653?journal_id=222782010-11-10T19:16:01ZOleg Volkov
<ul></ul><p>$ patch -p 1 <../redmine_own_v.2.patch</p> Redmine - Feature #2653: New permission for issues: view_own_issuehttps://www.redmine.org/issues/2653?journal_id=222792010-11-10T22:39:44ZDov Amihod
<ul></ul><p>Hi Oleg,</p>
<p>I've done as you advised ( and took the chance to update to 1.0.3) and it has worked.</p>
<p>Thanks for your help.</p>
<p>Dov</p> Redmine - Feature #2653: New permission for issues: view_own_issuehttps://www.redmine.org/issues/2653?journal_id=225132010-11-17T15:25:44ZSam Kuper
<ul></ul><p>Eric Davis wrote:</p>
<blockquote>
<p>Assigning this to myself so I remember to review it once I'm done with a book launch.</p>
</blockquote>
<p>I read this and thought, "Nice! His book has been launched now, if I'm not mistaken, so hopefully that will mean this patch will make it into core soon." But then I read this:</p>
<p>Eric Davis wrote:</p>
<blockquote>
<ul>
<li>Assignee deleted (Eric Davis)</li>
</ul>
</blockquote>
<p>and thought, "Er, that's a bit disappointing. Is this patch going to make it into core or not?"</p> Redmine - Feature #2653: New permission for issues: view_own_issuehttps://www.redmine.org/issues/2653?journal_id=225142010-11-17T16:15:16ZOleg Volkov
<ul></ul><p>IRC Log:</p>
<p>Q: Feature <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: New permission for issues: view_own_issue (Closed)" href="https://www.redmine.org/issues/2653">#2653</a>, Assignee deleted (Eric Davis), why?<br />E.Davis Answer: I'm limiting the amount of time I'm giving to Redmine now and that feature isn't something I'm interesting in</p> Redmine - Feature #2653: New permission for issues: view_own_issuehttps://www.redmine.org/issues/2653?journal_id=225172010-11-17T18:09:36ZEric Davis
<ul></ul><p>Sorry if I disappointed you Sam Kuper, things have been getting pretty busy with Redmine and my plugins (I have 250 emails/patches to review for my plugins alone, not even counting the Redmine core). With 1.1 coming out soon, I've been focusing on the last features decided on from the <a class="wiki-page" href="https://www.redmine.org/projects/redmine/wiki/TeamLeadMeeting3">TeamLeadMeeting3</a>. <strong>And</strong> if that wasn't enough, several major things are on hold for me too (<a href="http://theadmin.org/articles/2010/11/15/things-on-hold/" class="external">backstory</a>).</p>
<p>Only thing I can suggest is to be patient. All of the contributors I know are aware of this feature request, it's just a problem of limited time right now.</p> Redmine - Feature #2653: New permission for issues: view_own_issuehttps://www.redmine.org/issues/2653?journal_id=225242010-11-17T23:32:53ZVictor Batista
<ul></ul><p>Hi<br />I have just installed the patch on redmine 1.0.1 with success. <br />Users without "View issue" and with "Add issue" can see all the issues on the list of issues, but can only see the details of the issues assigned to them (HTTP 403 for not owned issues).<br />My doubt is: Should the user view, on the list of issues, issues which are not assigned to him?</p>
<p>Thanks for your time.<br />Best regards,<br />Victor Batista</p> Redmine - Feature #2653: New permission for issues: view_own_issuehttps://www.redmine.org/issues/2653?journal_id=225322010-11-18T16:27:58ZSam Kuper
<ul></ul><p>Oleg Volkov wrote:</p>
<blockquote>
<p>IRC Log:</p>
<p>Q: Feature <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: New permission for issues: view_own_issue (Closed)" href="https://www.redmine.org/issues/2653">#2653</a>, Assignee deleted (Eric Davis), why?<br />E.Davis Answer: I'm limiting the amount of time I'm giving to Redmine now and that feature isn't something I'm interesting in</p>
</blockquote>
<p>Eric Davis wrote:</p>
<blockquote>
<p>Sorry if I disappointed you Sam Kuper, things have been getting pretty busy with Redmine and my plugins (I have 250 emails/patches to review for my plugins alone, not even counting the Redmine core). With 1.1 coming out soon, I've been focusing on the last features decided on from the <a class="wiki-page" href="https://www.redmine.org/projects/redmine/wiki/TeamLeadMeeting3">TeamLeadMeeting3</a>. <strong>And</strong> if that wasn't enough, several major things are on hold for me too (<a href="http://theadmin.org/articles/2010/11/15/things-on-hold/" class="external">backstory</a>).</p>
<p>Only thing I can suggest is to be patient. All of the contributors I know are aware of this feature request, it's just a problem of limited time right now.</p>
</blockquote>
<p>Hi Eric, thanks for clarifying (and Oleg for also helping to clarify Eric's reasons). And fair enough, too; I've sympathy with being overstretched! I've just not seen devs un-assign tasks to themselves like this before.</p>
<p>Now that I understand what's going on, I agree it's actually quite a good way of saying to the public: "My backlog is so long right now that leaving this item on it gives the false impression I might actually get it done in a satisfactory timeframe!"</p>
<p>I'm tempted to become a Redmine dev myself so that I can work on some of these issues, but have a fair backlog of my own to clear before I might be able to manage that. I'd want to read your book first, too :)</p> Redmine - Feature #2653: New permission for issues: view_own_issuehttps://www.redmine.org/issues/2653?journal_id=225402010-11-18T20:35:20ZEric Davis
<ul></ul><p>Sam Kuper wrote:</p>
<blockquote>
<p>Now that I understand what's going on, I agree it's actually quite a good way of saying to the public: "My backlog is so long right now that leaving this item on it gives the false impression I might actually get it done in a satisfactory timeframe!"</p>
</blockquote>
<p>Exactly. Also lets the other contributors know that I'm not actively working on it so they can pick it up if they want to. (Might be time to take this conversation off the issue and to the forum, I don't want to clutter up this issue with unneeded content).</p> Redmine - Feature #2653: New permission for issues: view_own_issuehttps://www.redmine.org/issues/2653?journal_id=235882010-12-31T11:30:52ZGermain SAVANNE
<ul></ul><p>Hi <br />is the patch <a class="external" href="http://www.redmine.org/attachments/download/4642/redmine_own_v.2.patch">http://www.redmine.org/attachments/download/4642/redmine_own_v.2.patch</a><br />compatible with the redmine version 1.0.4 and 1.0.5 ? <br />Thanks</p> Redmine - Feature #2653: New permission for issues: view_own_issuehttps://www.redmine.org/issues/2653?journal_id=235892010-12-31T11:49:16ZOleg Volkov
<ul></ul><p>I have not tested.</p> Redmine - Feature #2653: New permission for issues: view_own_issuehttps://www.redmine.org/issues/2653?journal_id=235962010-12-31T15:09:58ZAnoop L
<ul></ul><p>Cheers Oleg Volkov !!!</p>
<p>It's wonderful patch. You have done this without any modification to the UI which makes it so simple.</p>
<p>It's working fine without any issues. I have tested this on Redmine versions 1.0.3, 1.0.4(copy of existing installation) and 1.0.5.</p>
<p>Thank you So much Oleg Volkov.</p> Redmine - Feature #2653: New permission for issues: view_own_issuehttps://www.redmine.org/issues/2653?journal_id=235992010-12-31T15:31:57ZTerence Mill
<ul></ul><p>Would be gerat if someone can update this issue with the <a href="/projects/redmine/activity?from=2010-05-05">description for the patch</a></p> Redmine - Feature #2653: New permission for issues: view_own_issuehttps://www.redmine.org/issues/2653?journal_id=244972011-01-26T11:09:41ZO G
<ul></ul><p>Oleg Volkov wrote:</p>
<blockquote>
<p>IRC Log:</p>
<p>Q: Feature <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: New permission for issues: view_own_issue (Closed)" href="https://www.redmine.org/issues/2653">#2653</a>, Assignee deleted (Eric Davis), why?<br />E.Davis Answer: I'm limiting the amount of time I'm giving to Redmine now and that feature isn't something I'm interesting in</p>
</blockquote>
<p>Can Oleg commit this?<br />Would be great to see this in the next Redmine release!</p> Redmine - Feature #2653: New permission for issues: view_own_issuehttps://www.redmine.org/issues/2653?journal_id=245632011-01-27T15:00:49ZAsmir Mustafic
<ul></ul><p>i need this pathc too!</p> Redmine - Feature #2653: New permission for issues: view_own_issuehttps://www.redmine.org/issues/2653?journal_id=248502011-02-04T19:26:23ZSpenser Jones
<ul><li><strong>File</strong> <a href="/attachments/5285">redmine_own_v.2.patch</a> <a class="icon-only icon-download" title="Download" href="/attachments/download/5285/redmine_own_v.2.patch">redmine_own_v.2.patch</a> added</li></ul><p>Here is a working patch for the current revision of 1.1-Stable (rev 4797)</p> Redmine - Feature #2653: New permission for issues: view_own_issuehttps://www.redmine.org/issues/2653?journal_id=248522011-02-05T00:46:01ZStanislav Grebenyukov
<ul></ul><p>Is any chance that this useful function sometime be a part of the trank? In revision 4794 patch doesn't work.</p> Redmine - Feature #2653: New permission for issues: view_own_issuehttps://www.redmine.org/issues/2653?journal_id=248532011-02-05T00:56:09ZStanislav Grebenyukov
<ul></ul><p>I meen rev. 4787</p>
<pre>
patch --dry-run -p1 < ./redmine_own_v.2.patch
patching file app/controllers/issues_controller.rb
Hunk #1 succeeded at 103 (offset 6 lines).
patching file app/models/issue.rb
Hunk #1 succeeded at 92 (offset 18 lines).
patching file app/models/query.rb
Hunk #1 succeeded at 389 with fuzz 1 (offset 10 lines).
Hunk #2 succeeded at 411 (offset 10 lines).
Hunk #3 succeeded at 502 (offset 51 lines).
patching file app/models/user.rb
Hunk #1 FAILED at 339.
Hunk #2 succeeded at 386 (offset 39 lines).
1 out of 2 hunks FAILED -- saving rejects to file app/models/user.rb.rej
patching file lib/redmine.rb
Hunk #1 succeeded at 45 (offset 1 line).
Hunk #2 succeeded at 59 (offset 1 line).
Hunk #3 FAILED at 95.
Hunk #4 succeeded at 122 (offset 1 line).
1 out of 4 hunks FAILED -- saving rejects to file lib/redmine.rb.rej
patching file test/fixtures/issues.yml
patching file test/fixtures/member_roles.yml
patching file test/fixtures/members.yml
patching file test/fixtures/roles.yml
Hunk #1 succeeded at 185 (offset 1 line).
patching file test/fixtures/users.yml
Hunk #1 succeeded at 152 with fuzz 2.
patching file test/fixtures/watchers.yml
patching file test/functional/issues_controller_test.rb
Hunk #1 succeeded at 311 (offset 34 lines).
Hunk #2 succeeded at 348 (offset 34 lines).
patching file test/unit/attachment_test.rb
Hunk #1 succeeded at 20 with fuzz 1.
patching file test/unit/issue_test.rb
Hunk #2 succeeded at 771 (offset 71 lines).
patching file test/unit/mailer_test.rb
patching file vendor/plugins/acts_as_attachable/lib/acts_as_attachable.rb
</pre> Redmine - Feature #2653: New permission for issues: view_own_issuehttps://www.redmine.org/issues/2653?journal_id=248542011-02-05T00:57:16ZStanislav Grebenyukov
<ul></ul><p>F**k (( rev 4797 :)</p> Redmine - Feature #2653: New permission for issues: view_own_issuehttps://www.redmine.org/issues/2653?journal_id=248562011-02-05T01:17:34ZBruno Medeiros
<ul></ul><p>Stanislav Grebenyukov wrote:</p>
<blockquote>
<p>Is any chance that this useful function sometime be a part of the trank? In revision 4794 patch doesn't work.</p>
</blockquote>
<p>Maybe on Redmine fork, ChiliProject, made by people who want to make a community-driven project:<br /><a class="external" href="https://www.chiliproject.org/projects/chiliproject/wiki/Why_Fork">https://www.chiliproject.org/projects/chiliproject/wiki/Why_Fork</a></p> Redmine - Feature #2653: New permission for issues: view_own_issuehttps://www.redmine.org/issues/2653?journal_id=248572011-02-05T01:52:08ZSpenser Jones
<ul></ul><p>Stanislav Grebenyukov wrote:</p>
<blockquote>
<p>Is any chance that this useful function sometime be a part of the trank? In revision 4794 patch doesn't work.</p>
</blockquote>
<p>If you use the patch I had added a few hours before you, it should run against 4797 just fine. Those two failed hunks were easily corrected.</p> Redmine - Feature #2653: New permission for issues: view_own_issuehttps://www.redmine.org/issues/2653?journal_id=293602011-05-30T19:22:25ZJean-Philippe Langjp_lang@yahoo.fr
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Closed</i></li><li><strong>Resolution</strong> set to <i>Duplicate</i></li></ul><p>Superseded by <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: Add an issue visibility level to each role (Closed)" href="https://www.redmine.org/issues/7412">#7412</a> added in 1.2.0.</p>