Feature #2128

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

Added by Mark Thomas almost 12 years ago. Updated about 4 years ago.

Status:NewStart date:2008-11-03
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:Issues
Target version:-
Resolution:

Description

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:
  1. Hide the Assigned-to field and show it only when the issue is assigned.
  2. Prevent a New issue from getting an assignment at all.
  3. Make the availability of the form field depend on user permission for Assignment in the workflow.
  4. 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.

Related issues

Related to Redmine - Feature #4582: Automaticly set an issue status when an issue is first as... New 2010-01-14

History

#1 Updated by Jean-Philippe Lang over 11 years ago

  • Tracker changed from Defect to Feature

#2 Updated by Benjamin Schunn about 4 years ago

this is already solved or I am wrong?

#3 Updated by Toshi MARUYAMA about 4 years ago

  • Category set to Issues

#4 Updated by Toshi MARUYAMA about 4 years ago

  • Related to Feature #4582: Automaticly set an issue status when an issue is first assigned added

Also available in: Atom PDF