プロジェクト

全般

プロフィール

Vote #77714

未完了

Issue visibility "watched by, created by or assigned to" for roles

Admin Redmine さんが約2年前に追加. 約2年前に更新.

ステータス:
New
優先度:
通常
担当者:
-
カテゴリ:
Issues permissions_23
対象バージョン:
-
開始日:
2022/05/09
期日:
進捗率:

0%

予定工数:
category_id:
23
version_id:
0
issue_org_id:
23546
author_id:
3866
assigned_to_id:
0
comments:
20
status_id:
1
tracker_id:
3
plus1:
0
affected_version:
closed_on:
affected_version_id:
ステータス-->[New]

説明

There's been a bit of discussion (parts of #8488 and other) and some patches already for this or similar (#14318#note-22) and others.

We wanted to contribute our "minimal" solution for this. This is a new ticket to avoid discussing ever more diverging patches on for example #8488.


journals

--------------------------------------------------------------------------------

--------------------------------------------------------------------------------

--------------------------------------------------------------------------------
I tested the patch and seems to work fine only for public projects. If I set the project as private, I can't see the issue anymore as watcher. This is the expected behavior?
--------------------------------------------------------------------------------
The patch should work for private projects too. However, in this case, you need to be a member of the project with a role which gives you:

* the permission to view issues,
* and the appropriate issue visibility
--------------------------------------------------------------------------------
Or, in other words - this new issue visibility option (like any of the other issue visiblity options) is not expected to give access to issues in projects where you don't have access to issues through your role's permissions. The goal is just to provide a slightly broader scope compared to the 'issues created by or assigned to the user' option.
--------------------------------------------------------------------------------
Jens Krämer wrote:
> Or, in other words - this new issue visibility option (like any of the other issue visiblity options) is not expected to give access to issues in projects where you don't have access to issues through your role's permissions. The goal is just to provide a slightly broader scope compared to the 'issues created by or assigned to the user' option.

Thanks, now is clear for me how should work.
--------------------------------------------------------------------------------

--------------------------------------------------------------------------------
I tested this with MySQL12 and Redmine 3.3.0 and I received a parsing error for users with watched permission for some projects and all issue for other projects. The apache logs claimed a parsing error SQL and the front end showed error 500 when trying to view all issues for all projects. Any suggestions on how to proceed? I'm very keen to see this implemented but my SQL knowledge is quite low.
--------------------------------------------------------------------------------

--------------------------------------------------------------------------------
You may be interested in "my last comment on #8488":/issues/8488#note-166 about this patch.
--------------------------------------------------------------------------------
@Felix, I've started to update the patches used in our instance to apply cleanly to Redmine version:3.4.1 and a test from this patch fails (ActiveRecord::RecordInvalid: Validation failed: Assignee is invalid).

I've updated your patch to pass the tests, please take a look on my changes to confirm that are ok (of course, if you want and have the time :) ).
--------------------------------------------------------------------------------

--------------------------------------------------------------------------------

--------------------------------------------------------------------------------
I am unable to install it.
I tried with these command:
patch -p0 < 23546-watched_or_created_or_assigned_issue_visibility_3.4.1.patch.

I got this error:

can't find file to patch at input line 4_ Perhaps you used the wrong -p or --strip option? The text leading up to this was:

|*** diff -Naur app/models/issue.rb ----- File to patch: –

Any ideas?
--------------------------------------------------------------------------------

--------------------------------------------------------------------------------

--------------------------------------------------------------------------------

--------------------------------------------------------------------------------

--------------------------------------------------------------------------------
Hi, any chance for updating this patch for Redmine 4.2? WIth new visibility feature userrs are seeing no tasks
--------------------------------------------------------------------------------


related_issues

relates,New,8488,Create an 'Involve' mechanism to private issues
relates,Closed,14318,Watchers Alerted To Changes But Cannot See Issues (potentially)
duplicates,Closed,27028,Issue's visibility for the watchers
duplicates,Closed,28223,Lack of access for Watchers if visibility=Issues created by or assigned to
duplicates,Closed,28614,Issue Watcher view Issue when not in project group
duplicates,Closed,32491,Watcher can see tickets independent from issue visibility

Admin Redmine さんが約2年前に更新

  • カテゴリIssues permissions_23 にセット

他の形式にエクスポート: Atom PDF

いいね!0
いいね!0