プロジェクト

全般

プロフィール

Vote #72022

未完了

Per-user closed status flag

Admin Redmine さんがほぼ4年前に追加. ほぼ4年前に更新.

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

0%

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

説明

The feature I would like to see is the ability to consider a status closed on a per-user basis.

Use case :

  • A developer user is completing "feature" issues. He wants to look at the roadmap and see the issues he has fixed as being closed - BUT
  • The tester is testing the "feature" issues. She wants to look at the roadmap and see features that have been released as open. When she sets the status to indicate that she has verified the feature works, she wants them to look closed.

This would work nicely with both the web UI and Mylyn to get features that are finished out of the way - from the point of view of the user viewing them.

I know that you can achieve some measure of this with queries.


journals

Well, this is more or less implemented at all. Those "close" flag isn't implemented, but you have the status resolved, which is pretty much the same. If the developer has his ticket view, filtered by tickets which are open and the ticket shouldn't have the status "resolved", he gets the requested view.
The tester could filter for tickets which are open or tickets which are resolved (depending on his view) and test those features. If the feature is implemented an works as expected, he could set the ticket to "closed".

I don't get the point, what's the benefit of your suggestion?
--------------------------------------------------------------------------------

Admin Redmine さんがほぼ4年前に更新

  • カテゴリIssues workflow_41 にセット

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

いいね!0
いいね!0