Redmine

Funny, I can't find the option to add a relation to a ticket when the issue is created, it is a bug ??

This ticket can be related to #337

I'd like to second the desire for this feature. We've been using Bugzilla as our issue tracker some time now. Bugzilla has the ability for private issues and private comments and I can say we use the private comments feature much more (although the private issue feature is helpful as well). Similar to what Philippe mentioned, we use the private comments to create clarification or ask questions internally that we would rather not share with our clients.

This actually has been the main issue causing us to hesitate in migrating to Redmine, although we will still probably jump in soon.

+1

+1. This would be very useful.

We also could really use this functionality. This actually more important than 'private issues'...

Seems to me that this could be handled pretty easily as a plugin... Does anybody know of one that does this?

JIRA uses a checkbox for marking a comment as private. I think, this would be a first quick hack.

I make the following changes in app/models/journal.rb:
def notes
orignote=read_attribute(:notes).to_s
if (User.current.allowed_to?(:privnote, project)||self.user.to_s==User.current.to_s)||(aa[0..0]!='/')
orignot
else
"private note!"
end
end

when the first char is '/' then the note value is "private note"
the :privnote is a new permission in lib/redmine.rb:
map.permission :felelos_valasztas, :issues => :felelos_valasztas
But this solution is bad for the mail notification.

+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 #1193.

chris madler wrote:

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 #1193.

This might be more easy to use than having Comment / Reply models ?
On the other hand, since redmine has automatic notification, it sounds silly to change (=hide) a ticket update after a mail is sent, so the couple Comment(hidden) / Reply(visible) should be considered too.

Thanks !

+1 definately.

This feature would be an awesome addition. Currently we use Redmine for larger projects. Both our developers as customers have access to the issue list and we have entire conversations regarding bugs/features in our applications. It would be great to have private comments that would be visible for only certain users or usergroups. That way we would be able to include internal task assignments in the comments without our customers being notified all the time.

+1

Philippe Lafoucrière wrote:

This might be more easy to use than having Comment / Reply models ?
On the other hand, since redmine has automatic notification, it sounds silly to change (=hide) a ticket update after a mail is sent, so the couple Comment(hidden) / Reply(visible) should be considered too.

How about new setting "private issues"

When selected, then all comments in private in default, until you click "Answer author" checkbox

Hows that sounds?

+1

Any news on this feature?
We use now a "internal" and a external project to hide comments and development steps to the customer. But they have to be on same status, so it's more work.

regards Ron

Feature #337 is updated for current trunk version.

Great, thanks. Anyway, I want to make sure we're talking about the same thing. This issue is about private COMMENTS in tickets. It's somehow related to #337, but they are really not the same feature request.
Thanks
Philippe

First you have to push in a trunk feature 337, then make private comments. Please test the feature 337.

Philippe Lafoucrière wrote:

Great, thanks. Anyway, I want to make sure we're talking about the same thing. This issue is about private COMMENTS in tickets. It's somehow related to #337, but they are really not the same feature request.

In the trunk version for private comments, it will create a subtask with a private issue.

I updated the # 337. Please test it.

Private notes are needed for NOT private issue?
Who should view private notes?

Oleg Volkov wrote:

I updated the # 337. Please test it.

Thanks Oleg, I'll test it.

Private notes are needed for NOT private issue?

Yes, privates notes and private issues are 2 different things. A ticket can be "public" (not private) and have private notes.

Who should view private notes?

This should be part of the roles configuration, but I'd say manager + developer. Generally, the reporter is the customer, they should not see private comments.

An example of private comment :

1- John_the_customer opens an issue : "I can't login on the demo site"
2- Bill_the_dev_leader adds a private comment : "Check that this jerk has created an account on demo, and if the last database has been imported"
3- Bob_the_dev adds a reply : "John, we'll check if you an account on demo, and if everything is in place and let you know asap".

John should not see step 2 :)

Privileges "Hidden notes" for the possibility of adding / editing / viewing of hidden notes will be enough?

Exactly!
Thanks

Would be great to have this feature, we'd also benefit greatly by being able to control which comments can be seen by customers. We also considered an internal/external project but this would be slow and cumbersome.

Would be very useful indeed. That way a person working on an issue can update the issue with information not visible for "plain" viewers. A discrete comment so to speak.

+1

+1

+1

+1

+1

+1

My organization is getting flustered with Redmine because there are no private comments. This would be a very good addition for us.

Thank you for private issue, now we are waiting for private comments.

Is anyone investigating this? This feature would greatly enhance our support environment.

Oleg Volkov wrote:

Privileges "Hidden notes" for the possibility of adding / editing / viewing of hidden notes will be enough?

Yes, this would be absolutely sufficient, thus this one is not dependent on #337

+1

+1

+1

+1

Mantis has that feature as well and we are using it a lot. Our customers uses our issue management system and in almost every ticket we need to discuss something, that the customer is not supposed to see.

Can't wait for this feature!

+1

+1 Is anyone on the Redmine team looking at putting this onto the roadmap? Thanks

+1 Thanks Etienne, I can't wait either :)

+ me too

+1

+1

+1

+1: necessary feature

+1:

+1

+1

+1
Please, implement this feature. My client shouldn't see programmer talks

Dmitry Polovka wrote:

As Eugene Kharkov mentioned before http://www.redmine.org/boards/1/topics/4325?r=25789#message-25789 Ruby and Rails not our strong side, so it would be nice if somebody of experienced Ruby developers cleaned up our code. We made patch from /branches/1.2-stable/ r6484 source code and added one permission "View private messages" which allow you view and also add private messages.

What I have to do with 20110820092133_add_private_to_journals.rb ?
I successfull patched the source, but I don't know how to change the database. Even with an "alter table journals add column private tinyint(1) default 0;" I cannot create a new notice.

NoMethodError in Issues#show
Showing app/views/issues/show.rhtml where line #94 raised:
undefined method `private' for #<Journal:0x4f8ec5c>

+1 Agreed - it would be very useful to be able to tag a comment as "private" or a drop-down that says "Make this comment viewable to: [All, Managers, Developers, Reporters]

I've applied the patch to a 1.2.1 installation, and everything appears to work as expected with the exception of the activity log. This still shows all comments, private and non-private. Is there a step I might have missed?

Resolved the activity log issue by adding:

        # The private notes should be removed from events
    events.delete_if { |e| e.is_a?(Journal) && e.private }

to app/controllers/activities_controller.rb

+1 on that feature...

Is anyone using the patch from Dmitry Polovka plus the additional change by Razi successfully? Is it safe to apply and try it out? Thanks!

Razi Baluchi wrote:

Resolved the activity log issue by adding:

[...]

to app/controllers/activities_controller.rb

This method of hiding the activity is going to hide the private notes regardless of whether you have permission to see them or not. I'll fix it and post a patch if I manage to fix it.

Shouldn't logic like this be going into the model, not the controller?

Forget my question i found how to do it

Alter Way wrote:

I am a newby on ruby: How do you run 20110820092133_add_private_to_journals.rb migration script ?
thx

Alter Way wrote:

I am a newby on ruby: How do you run 20110820092133_add_private_to_journals.rb migration script ?
thx

Please don't randomly assign tickets to people.

My initial thought is that you might not be running it from your redmine install directory. I occasionally get error like that when I try to apply a patch from ~/

This also might be caused if you've made modifications to redmine yourself or run a previous patch first. You really only need to run the last patch posted.

+1

I am really looking forward to this feature. I've been missing this since I last used Bugzilla years ago.

+1 I really need this feature. Hope it will be included in the next release. But first i try the patch right now.
Patch doesn´t work. I get the same errors as Pablo Bastari http://www.redmine.org/issues/1554#note-65.
I am in the redmine root and didn´t modify it.

+1

+1

+1

+1 ASAP

We're using the 1.3.x patch. Can anybody please provide an update for 1.4.x?
Since this issue is +4 years old, who can push this issue from "Candidate for next major release" really to next major release?

+1
Would be a huge step forward for our use case.

+1
This feature could make us replace Jira (one thing that we would like to see in redmine in order to make a transition)!

+1

How would I get the messages to be private by default? I.e. where the tickbox is shown, have it selected by default?

Vicky Dibble wrote:

How would I get the messages to be private by default? I.e. where the tickbox is shown, have it selected by default?

I worked this out, if you edit
/opt/bitnami/apps/redmine/app/views/issues/_edit.html

And change

<% if view_private >
       <= check_box_tag :private_message, true, false >
       <= label_tag :private_message, 'Private message', :style => 'font-weight:bold;' >
     < end %>

to be

<% if view_private >
       <= check_box_tag :private_message, true, false, :checked => true >
       <= label_tag :private_message, 'Private message', :style => 'font-weight:bold;' >
     < end %>

Then where the 'Private' check box for messages appears, it sets it as ticked.
I have set up and tested this in 1.4 with the patches above. Great work all told guys, and a massive plus for Redmine. Thanks!

This shall be configurable in global settings.
Also private issues default shall be configurable in global settings.

-1 for using just a flag for "private" vs. "non-private" as that is very limited...
+1 for a feature to be able to set the "visibility/viewing-restriction" of a comment to all users/a role/a group or even selected users.

Martin S. wrote:

+1 for a feature to be able to set the "visibility/viewing-restriction" of a comment to all users/a role/a group or even selected users.

This is overkill IMO. I'm not saying that it would be useless but still, this feature will be implemented as a simple flag in 2.2 and visibility configured on each role.

Jean-Philippe Lang wrote:

Martin S. wrote:

+1 for a feature to be able to set the "visibility/viewing-restriction" of a comment to all users/a role/a group or even selected users.

This is overkill IMO. I'm not saying that it would be useless but still, this feature will be implemented as a simple flag in 2.2 and visibility configured on each role.

I agree. Let's make the basic functionality a standard feature, and provide the rest (which only a few will need) through a plugin...

Jean-Philippe Lang wrote:

this feature will be implemented as a simple flag in 2.2 and visibility configured on each role.

When you say a flag, are you referring to a flag on the ticket or on each individual comment? My apologies if you've already answered this.

Deoren Moor wrote:

When you say a flag, are you referring to a flag on the ticket or on each individual comment? My apologies if you've already answered this.

On each comment.

This one would be very helpful! We're thinking about a implementation of redmine in our current workflow and have many tasks where private comments would solve our problems!

Jean-Philippe Lang wrote:

Deoren Moor wrote:

When you say a flag, are you referring to a flag on the ticket or on each individual comment? My apologies if you've already answered this.

On each comment.

That's awesome. I'm really excited about this feature.

Just a note about comment numerotation and #2715:

As some comment will be private, there will be gaps in numerotation for users that aren't allowed to see private comments (there must be gaps because of #2715).

So maybe we can take advantage of this new issue to make this numerotation more consistent?
As it is for now, you can pseudo-delete a comment by specifying an empty text so the comment will not be visible by anyone and numerotation will be different starting from this comment, thus broking #2715.

Last thing, maybe that the same visibility setting could be used for comments and issue?

I'm thrilled to hear that 2.2 will include Private Comments! Our team intends to use Redmine as a way to help keep our clients updated, but sometimes as developers we deal with information that will only confuse (or even unduly alarm) the non-techie types. I do have a quick request, though:

Can we make "Private" the default value for the flag?

I'd just hate for one of our developers to forget to tick the "Private" box on a client issue and end up complicating an otherwise trivial support issue. Thanks!

Brian Lacy wrote:

Can we make "Private" the default value for the flag?

This can't be the default behaviour. But we could make it configurable, maybe globally or on a per user or role basis?

Jean-Philippe Lang, is the revision change stable?
I will love to test the private comment feature.

Current trunk is pretty stable. It would nice if you could give it a try before 2.2 release.

Just tested it, it looks great! I didn't know there was some work going on here, so last week I released a very basic plugin that achieves the same idea (redmine_comments), but it looks a bit pathetic now ;) People who need this feature in Redmine 2.1.x can try my plugin though, I'll try to handle the transition to the core feature as soon as 2.2.0 is out. Thanks for this feature!

Jean-Philippe Lang wrote:

Brian Lacy wrote:

Can we make "Private" the default value for the flag?

This can't be the default behaviour. But we could make it configurable, maybe globally or on a per user or role basis?

Per role would be great and very useful, same for default issue level.

Tested also, nice job indeed. Only remark, the french label associated with the 'Private note' checkbox in the upadte issue form is in plural form.

Etienne Massip wrote:

Jean-Philippe Lang wrote:

Brian Lacy wrote:

Can we make "Private" the default value for the flag?

This can't be the default behaviour. But we could make it configurable, maybe globally or on a per user or role basis?

Per role would be great and very useful, same for default issue level.

Tested also, nice job indeed. Only remark, the french label associated with the 'Private note' checkbox in the upadte issue form is in plural form.

+1

I've created a plugin to enforce private notes for a role by default.
See https://github.com/githubnemo/Redmine-Private-Note-Enforcment

Only recent versions output if a note is private

https://github.com/redmine/redmine/commit/0e59482e90a788f2da7775a3fb5c51dbea7b135f