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:

1        # The private notes should be removed from events
2    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.