Project

General

Profile

Actions

Feature #7414

closed

Private issues

Added by Jean-Philippe Lang almost 14 years ago. Updated about 13 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Issues permissions
Target version:
Start date:
2011-01-22
Due date:
% Done:

0%

Estimated time:
Resolution:
Fixed

Description

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).


Files

private_issue.png (3.76 KB) private_issue.png Jean-Philippe Lang, 2011-04-15 15:36

Related issues

Related to Redmine - Feature #8424: Add private issue option to receiving emailsClosedJean-Philippe Lang2011-05-23

Actions
Related to Redmine - Defect #8432: Private issues information shows up on Activity page for unauthorized usersClosed2011-05-25

Actions
Related to Redmine - Feature #8488: Create an 'Involve' mechanism to private issuesNew

Actions
Related to Redmine - Feature #8577: "Private" column and filter on the issue listClosedJean-Philippe Lang2011-06-09

Actions
Related to Redmine - Feature #9067: Private tasks - wouldn't be shown in activityClosed2011-08-16

Actions
Related to Redmine - Feature #9209: Add "Private" toggle to issue context menuNew

Actions
Related to Redmine - Feature #9432: Default value for the private issue flagNew2011-10-17

Actions
Related to Redmine - Defect #10148: Private issue in public projectsClosed2012-02-03

Actions
Has duplicate Redmine - Feature #337: Private issuesClosedJean-Philippe Lang

Actions
Has duplicate Redmine - Feature #3384: issue permissionsClosed2009-05-18

Actions
Actions #1

Updated by Damien Couderc almost 14 years ago

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

Actions #2

Updated by Anonymous over 13 years ago

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) :)

Actions #3

Updated by Ryan Cross over 13 years ago

Why not use the same interface paradigm as the notifications?

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

Actions #4

Updated by Nuno Duarte over 13 years ago

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

Actions #5

Updated by Alfredo Bonilla over 13 years ago

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

Actions #6

Updated by Giulio Turetta over 13 years ago

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

Actions #7

Updated by Roland Discein over 13 years ago

+1

Actions #8

Updated by Daniel Herrera over 13 years ago

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

Actions #9

Updated by Jean-Jacques Mérillon over 13 years ago

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

Actions #10

Updated by Jean-Philippe Lang over 13 years ago

It won't be moved.

Actions #11

Updated by Anton Lukashev over 13 years ago

That's great! Looking forward for it.

Actions #12

Updated by Jean-Philippe Lang over 13 years ago

Feature added in r5466.

Two new permissions are now available:

  • Set issues public or private => will let the user set/change the private flag on issues that he creates or edits
  • Set own issues public or private => will let the user set/change the private flag on his own issues

A new issue visibility level is available on roles:

  • All non private issues => user will see all non private issues and private issues that were created by him or are assigned to him
Actions #13

Updated by Vlad Vlad over 13 years ago

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.

Actions #14

Updated by Etienne Massip over 13 years ago

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.

Actions #15

Updated by Frank Helk over 13 years ago

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.

Actions #16

Updated by Roman E. over 13 years ago

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.

Actions #17

Updated by Bruno Medeiros over 13 years ago

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

Actions #18

Updated by Martin G over 13 years ago

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

Actions #19

Updated by Bruno Medeiros over 13 years ago

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.

Actions #20

Updated by Pavel Konstantinov over 13 years ago

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

Actions #21

Updated by Bruno Medeiros over 13 years ago

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.

Actions #22

Updated by Reuben Schreiber about 13 years ago

SPAM

Actions #23

Updated by Martin G about 13 years ago

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

Actions

Also available in: Atom PDF