Feature #1193: Staff-only notes with Role-base access control - Redmine

Feature #1193

Staff-only notes with Role-base access control

Added by Dmitry Isanov almost 13 years ago. Updated almost 2 years ago.

Status:

New

Start date:

2008-05-06

Priority:

Normal

Due date:

Assignee:

% Done:

Category:

Permissions and roles

Target version:

Resolution:

Description

I'm sure that the following would be really useful:

to have the special category of the Issue Notes - Staff-only Notes, with Role-based access/visibility control.
It would allow to put there information, hint, ets. that shouldn't be visible to specified Role (say, Customer).

Really eager to have it!

Thanks,
Dmitry

Related issues

History

#1 Updated by Fabrice Phung almost 13 years ago

I totally agree with this feature usefulness. I see it as a 'private' attribute triggering note display for specified roles. The drawback is that nobody sees the same content.

#2 Updated by Tommy Jensen almost 13 years ago

#3 Updated by Benjamin Baroukh almost 13 years ago

#4 Updated by Ronie Henrich almost 13 years ago

#5 Updated by Thomas Pihl over 12 years ago

#6 Updated by Paolo Sulprizio over 12 years ago

#7 Updated by Toni Kerschbaum over 12 years ago

#8 Updated by Arndt Lehmann over 12 years ago

#9 Updated by Jean-Philippe Lang over 12 years ago

Target version deleted (~~0.8~~)

#10 Updated by Szabolcs Klement almost 12 years ago

#11 Updated by Jens Goldhammer almost 12 years ago

#12 Updated by Shaun Gilroy over 11 years ago

This issue is duplicated in 1554, I think.

#13 Updated by chris madler over 11 years ago

+1
I also think this feature is absolutely necessary for companies that want to keep some notes on issues only visible to staff members and other notes (also) visible to clients.

I suppose it would consist of having a field "visibility" with values (private, public) on each note that is added to an issue. Then in roles, a permission to view certain visibility values (private, public, or both?). Related to #1554.

#14 Updated by Paolo Sulprizio over 11 years ago

+1
It would be also useful to define the default setting (private, public) on per-project basis. It could permit to create project in which only visible issues' information for clients are description and state.