Feature #1193

Staff-only notes with Role-base access control

Added by Dmitry Isanov over 9 years ago. Updated about 3 years ago.

Status:ClosedStart date:2008-05-06
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:Permissions and roles
Target version:-
Resolution:Duplicate

Description

Hi

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

Duplicates Redmine - Feature #1554: Private comments in tickets Closed 2008-06-30

History

#1 Updated by Fabrice Phung over 9 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 over 9 years ago

+1

#3 Updated by Benjamin Baroukh over 9 years ago

+1

#4 Updated by Ronie Henrich over 9 years ago

+1

#5 Updated by Thomas Pihl over 9 years ago

+1

#6 Updated by Paolo Sulprizio over 9 years ago

+1

#7 Updated by Toni Kerschbaum about 9 years ago

+1

#8 Updated by Arndt Lehmann about 9 years ago

+1

#9 Updated by Jean-Philippe Lang about 9 years ago

  • Target version deleted (0.8)

#10 Updated by Szabolcs Klement over 8 years ago

+1

#11 Updated by Jens Goldhammer over 8 years ago

+1

#12 Updated by Shaun Gilroy over 8 years ago

This issue is duplicated in 1554, I think.

#13 Updated by chris madler about 8 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 about 8 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.

#15 Updated by Oleg Volkov over 7 years ago

See features #337. This is private Issue. Please test it.
Private Issue Notes - second step (see #1554 too).

#16 Updated by Go MAEDA over 3 years ago

Private issue note which have been introduced in Redmine 2.2(#1554).
This issue can be closed.

#17 Updated by Etienne Massip over 3 years ago

#18 Updated by Etienne Massip over 3 years ago

  • Status changed from New to Resolved
  • Resolution set to Duplicate

Indeed.

#19 Updated by Alex Alex over 3 years ago

+1

#20 Updated by Toshi MARUYAMA about 3 years ago

  • Status changed from Resolved to Closed

Also available in: Atom PDF