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.

Add new issue status to all workflows by default (Feature #616)

Added by Jan Schulz-Hofen at 2011-09-11 05:13 pm. Updated at 2012-08-29 06:53 am.

Status:Open Start date:2011-09-11
Priority:Normal Due date:
Assignee:- % Done:


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


At Planio Online Project Management which is based on Redmine, we keep getting user feedback about the following situation:

A new user tries to add an issue status. He/She successfully finds the "Issue Statuses" section within "Administration" and adds a new status but gets confused that the status cannot be assigned when creating or updating an issue. Many users give up at this point and we need to help them explaining how to find and use the "Workflow" section. The "Only display statuses that are used by this tracker" checkbox (which is checked by default) represents another common pitfall as a newly created status won't be available in the matrix unless the checkbox is unchecked.

In an attempt to improve the situation, we created this patch. It adds a checkbox to the "New status" view allowing the user to add the to-be-created status to all workflows by default. The checkbox is checked by default, but it can be unchecked by advanced users who only want to use the new status in certain workflows. We have found that in many cases, teams aren't making use of Redmine's great role-based workflow permission system. Instead, many allow everyone on a project to use every issue status. This patch helps those users all while allowing advanced admins to configure the fine-grained permissions on workflows.

Looking forward to your feedback and would love to see this getting into the core. We believe it will help first-time Redmine users adopt and learn Redmine.

N.B. The feature becomes a performance problem once there are many issue statuses/roles/trackers. Improvements (using raw SQL?) are welcome. We went for the ActiveRecord based approach, because it's easier to maintain and less likely to break with future Redmine changes.

Patch is against our version of Redmine. Should be easy to adapt.

changeset_r9e80ae182e30c58857c8e30260f7fc3788dd7597.diff (30.7 kB) Jan Schulz-Hofen, 2011-09-11 05:13 pm

Associated revisions

Revision 4dc7f662
Added by Jean-Philippe Lang at 2008-02-12 10:43 pm

Added issue subject to the time entries view and subject + tracker to the csv export (#616). Default order on date column set to desc.

git-svn-id: e93f8b46-1217-0410-a6f0-8f06a7374b81

Also available in: Atom PDF