Feature #9226

Add new issue status to all workflows by default

Added by Jan from Planio www.plan.io about 6 years ago. Updated almost 5 years ago.

Status:NewStart date:2011-09-11
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:Issues workflow
Target version:-
Resolution:

Description

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.

changeset_r9e80ae182e30c58857c8e30260f7fc3788dd7597.diff Magnifier (30.7 KB) Jan from Planio www.plan.io, 2011-09-11 19:08

changeset_a34bffe750ce27d8cda5fa83e60f5ff5525054fd.diff Magnifier (25.4 KB) Yehuda Katz, 2012-10-12 21:53


Related issues

Duplicates Redmine - Feature #9121: New statuses not available for use New 2011-08-25

History

#1 Updated by Jan from Planio www.plan.io about 6 years ago

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.

#2 Updated by Etienne Massip about 6 years ago

Duplicates #9121 which description is not as complete so I keep this one open.

#3 Updated by Yehuda Katz about 6 years ago

Duplicate comment from #9121

The patch works for me.
My only comment is that it appears that the built-in workflows leave the diagonal line of status->itself unchecked. Not sure if that really matters.

#4 Updated by Jan from Planio www.plan.io about 6 years ago

I don't think it does from a functionality point of view, but it seems to be the right thing to be in line with the default workflows. Plus, it will improve the performance a bit.

Just removing line 24

Workflow.create! :tracker_id => tracker.id, :old_status => @issue_status, :new_status => @issue_status, :role => role # self-to-self

from the patch will accomplish that. I'll leave that to the person committing this.

#5 Updated by Yehuda Katz about 5 years ago

Updated patch for Redmine current trunk.

#6 Updated by Yehuda Katz about 5 years ago

That patch does not seem to be working. I will test more, but don't use it.

#7 Updated by Daniel Felix almost 5 years ago

Yehuda Katz wrote:

That patch does not seem to be working. I will test more, but don't use it.

Any news on this?

Also available in: Atom PDF