Redmine

Shouldn't issue #337 be linked or closed in favor of this new issue ?

I'm singing up for this feature too...

I would suggest (if I can :) ) if it would be user group-based?

details:
For example, we have group Clients (which are in each project different set of people),
and in one project, we have issues that are only for group Developers...
Client MUSTN'T see them, because they contain confidental information (tickets shared with other dev group)...

I'm up for group-based permission per-ticket...
I don't know what you mean by permission-based privileges (haven't read the whole ticket #337, it's so damn long) :)

Why not use the same interface paradigm as the notifications?

I would also like to add groups to that though too.

Jean-Philippe Lang wrote:

The change consists in adding a 'private flag' on issues.
Users are allowed to view private issues in respect to their issue visibility level (#7412).

I Vote for this one as well

Please... do not move again to another version... we're waiting for this issue long time ago... ;(

Please... do not move again to another version... (2X)

+1

+1
This is a great feature that we miss in Redmine.

Please... do not move again to another version... we're waiting for this issue long time ago... ;( (3X)

It won't be moved.

That's great! Looking forward for it.

May I set the Private status on a Comment level? This I could have a public Issue with a private and public comunication at one place.

Vlad Vlad wrote:

May I set the Private status on a Comment level? This I could have a public Issue with a private and public comunication at one place.

This is the subject of #1554.

Question on that:

May I customize the privacy state of newly created tickets, i.e. in project config ? I not, I would recommend that as useful extension of that feature.

Can anyone tell if it is possible to reverse the feature. Meaning this:

We have a private project for administrative issues but sometimes people from other projects may need to access this single issue. In Bugzilla that we were used to, it was achievable via CC - by adding an individual to CC gives him access to to the specific issue.

Roman E. wrote:

We have a private project for administrative issues but sometimes people from other projects may need to access this single issue. In Bugzilla that we were used to, it was achievable via CC - by adding an individual to CC gives him access to to the specific issue.

It was discussed on #7412, but the way we suggested there to accomplish that was not the best. I just created a feature request to this, as suggested by Jean-Phillipe: #8488

Watchers of an issue are not able to see private issues. Is this wanted so?

Martin G wrote:

Watchers of an issue are not able to see private issues. Is this wanted so?

Watcher mechanism don't affect the issue visibility. To further info, please read #7412 / #8488.

Can I predefine initial state of Private flag for new issues? I need it to be checked by default

Pavel Konstantinov wrote:

Can I predefine initial state of Private flag for new issues? I need it to be checked by default

I need the same, but didn't realize how to do it. I guess we'll need a patch...
Maybe it is a good idea create a separate issue for that.

SPAM

Bruno Medeiros wrote:

Pavel Konstantinov wrote:

Can I predefine initial state of Private flag for new issues? I need it to be checked by default

I need the same, but didn't realize how to do it. I guess we'll need a patch...
Maybe it is a good idea create a separate issue for that.

See #9432