プロジェクト

全般

プロフィール

Vote #70704

未完了

Add new issue status to all workflows by default

Admin Redmine さんが約2年前に追加. 約2年前に更新.

ステータス:
New
優先度:
通常
担当者:
-
カテゴリ:
Issues workflow_41
開始日:
2011/09/11
期日:
進捗率:

0%

予定工数:
category_id:
41
version_id:
32
issue_org_id:
9226
author_id:
347
assigned_to_id:
0
comments:
9
status_id:
1
tracker_id:
2
plus1:
0
affected_version:
closed_on:
affected_version_id:
ステータス-->[New]

説明

At "Planio Online Project Management":http://plan.io/ 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.


journals

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.
--------------------------------------------------------------------------------
Duplicates #9121 which description is not as complete so I keep this one open.
--------------------------------------------------------------------------------
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.
--------------------------------------------------------------------------------
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 <pre>Workflow.create! :tracker_id => tracker.id, :old_status => @issue_status, :new_status => @issue_status, :role => role # self-to-self</pre>

from the patch will accomplish that. I'll leave that to the person committing this.
--------------------------------------------------------------------------------
Updated patch for Redmine current trunk.
--------------------------------------------------------------------------------
That patch does not seem to be working. I will test more, but don't use it.
--------------------------------------------------------------------------------
Yehuda Katz wrote:
> That patch does not seem to be working. I will test more, but don't use it.

Any news on this?

--------------------------------------------------------------------------------

--------------------------------------------------------------------------------

--------------------------------------------------------------------------------


related_issues

relates,Closed,30916,Show warning when no tracker uses the status in the workflows
duplicates,New,9121,New statuses not available for use

Admin Redmine さんが約2年前に更新

  • カテゴリIssues workflow_41 にセット
  • 対象バージョンCandidate for next major release_32 にセット

他の形式にエクスポート: Atom PDF

いいね!0
いいね!0