プロジェクト

全般

プロフィール

Vote #64600

未完了

Search and stats on workflow transitions

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

ステータス:
New
優先度:
通常
担当者:
-
カテゴリ:
-
対象バージョン:
-
開始日:
2009/02/05
期日:
進捗率:

0%

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

説明

I do get some questions over and over from a few (very agile and reflective) customers. They go something like this:

How many (and what) issues passed "Queue to Backoffice" workflow-step (for a specific category or some other filter)?

What issues was tested by insert tester.

Who is our "best" tester (as defined in 2 above)

How many (and what) issues are at or have passed workflow-step "Approved by customer". First part of question is easy, the second is not.

I would assume most people solve this with (redundant) extra custom fields tracking the above information (like tester or a checkbox for apprived by customer). Well, i do that too, but it's not all that good. I cannot handle retest and worst case i does contain the wrong info (i did the test and updated the issue but forgot to set the field).

I know the tables and i do take some of this info via SQL (some joins) but would love to get it via GUI (and in summary).

Is this a need for the rest of you as well?

/T


journals

> Is this a need for the rest of you as well?

I don't have a need for it because my workflow is really open (anyone can change an issue to any status) but it might be useful to others.
--------------------------------------------------------------------------------
+1. It would be good to have essentially having filtering and sorting based on journal data!
--------------------------------------------------------------------------------

表示するデータがありません

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

いいね!0