プロジェクト

全般

プロフィール

Vote #64088

未完了

Problems when 'Assigned To' field doesn't match 'Assigned' issue tracker

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

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

0%

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

説明

There are problems when the Assigned To field is set, but the issue tracker is not set to assigned. A non-member can set the Assigned-To field even when they don't have permission to make the issue assigned. The issue then shows up in the assignee's "Issues assigned to me" area even when it has not been officially assigned.

Note that others struggle with this issue as well. See also #349, #640, and #1919.

I can think of a few potential solutions:

Hide the Assigned-to field and show it only when the issue is assigned.

Prevent a New issue from getting an assignment at all.

Make the availability of the form field depend on user permission for Assignment in the workflow.

Add new permissions for the Assigned-To field (and perhaps others as mentioned in #1919) so that non-members can be denied the ability to change it.


journals

--------------------------------------------------------------------------------
this is already solved or I am wrong?
--------------------------------------------------------------------------------

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

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


related_issues

relates,New,4582,Automaticly set an issue status when an issue is first assigned

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

  • カテゴリIssues_2 にセット

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

いいね!0
いいね!0