I'm looking for a part-time remote job.

Hire me


I'm the author of:

Mastering Redmine is a comprehensive guide with tips, tricks and best practices, and an easy-to-learn structure.

Check the book's project or

Buy the book

Social pages of the book:

By buying this book you also donate to Redmine (see this page).


Follow me:

Feature #1983

Default shifts

Added by Andriy Lesyuk over 7 years ago.

Status:
Open
Priority:
Major
Assignee:
Target version:
-
Start date:
19 Feb 2012
Due date:
% Done:

0%

External issue:

Description

Saying you have 3 proprietary and 50 open source projects. The easiest way is to allow Anonymous and Non members to access projects and shift these roles for proprietary ones... But this method is not recommended - basic roles should always be more strict than their shifts (for a case something goes wrong and the plugin stops to work)! So looks like one is better to define shifts for 50 projects... It’s approximately 100 shifts... And similar shifts should be defined for each new open source project!..

So to avoid this the idea is to define global default shifts which get automatically created when a new project is registered. In this case for proprietary projects you will just need to remove these shifts...

Also available in: Atom PDF

Terms of use | Privacy policy