ChiliProject is not maintained anymore. Please be advised that there will be no more updates.

We do not recommend that you setup new ChiliProject instances and we urge all existing users to migrate their data to a maintained system, e.g. Redmine. We will provide a migration script later. In the meantime, you can use the instructions by Christian Daehn.

Private Issues and Private Comments (Feature #701)


Added by Simon Stearn at 2011-11-15 02:42 pm. Updated at 2011-11-15 02:56 pm.


Status:Declined Start date:2011-11-15
Priority:Normal Due date:
Assignee:- % Done:

0%

Category:-
Target version:-
Remote issue URL: Affected version:

Description

Is there a plan to pull in these features (initially included in Redmine 1.2 and due to be enhanced later). These are important for anyone using a server for mixed internal and external communication scenarios.


Related issues

duplicates Feature #189: Private/hidden issues Open 2011-02-13

Associated revisions

Revision d461363d
Added by Jean-Philippe Lang at 2008-02-21 06:50 pm

Fixed: Adding time when Updating a ticket is gone (closes #701).

git-svn-id: http://redmine.rubyforge.org/svn/trunk@1165 e93f8b46-1217-0410-a6f0-8f06a7374b81

History

Updated by Holger Just at 2011-11-15 02:56 pm

We are not really convinced of the way this was implemented in Redmine. See #189 for more information.

For now you would have to use separate (sub-)projects. For most people, this is a good-enough workaround. And for all I'm aware of, this can almost fully replace the functionality Redmine provides. That said, we are aware that private issues (or more generically private objects) is a useful feature which we are going to implement once we have the necessary base work done.

Closing this issue as a duplicate of #189.

  • Status changed from Open to Declined

Also available in: Atom PDF