Project

General

Profile

Actions
Copy link

Defect #21477

closed

Assign to "Anonymous" doesn't make much sense

Added by Felix Schäfer almost 9 years ago. Updated about 8 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Jean-Philippe Lang
Category:
Issues
Target version:
3.1.4
Start date:
Due date:
% Done:

0%

Estimated time:
Resolution:
Fixed
Affected version:

Description

Issues might be created by "Anonymous" (most prominent example would be via email). The author is added to the list of assignable users, which doesn't make much sense.

I will provide a patch to not add the author to the list of assignable users if the author is anonymous.

Files

21477-dont_add_anonymous_author_to_assignable_users.diff (452 Bytes) 21477-dont_add_anonymous_author_to_assignable_users.diff Felix Schäfer, 2015-12-10 18:17
Actions
Copy link
 #2

Updated by Jan from Planio www.plan.io almost 9 years ago

  • Target version set to Candidate for next minor release
Actions
Copy link
 #3

Updated by Jean-Philippe Lang almost 9 years ago

  • Category set to Issues
  • Status changed from New to Resolved
  • Assignee set to Jean-Philippe Lang
  • Target version changed from Candidate for next minor release to 3.2.1
  • Resolution set to Fixed

Thanks.

Actions
Copy link
 #4

Updated by Felix Schäfer almost 9 years ago

Not adding locked users seems sensible too, hadn't thought of that.

Thanks JPL.

Actions
Copy link
 #5

Updated by Jean-Philippe Lang almost 9 years ago

  • Target version changed from 3.2.1 to 3.1.4
Actions
Copy link
 #6

Updated by Jean-Philippe Lang almost 9 years ago

  • Status changed from Resolved to Closed
Actions
Copy link
 #7

Updated by Fran Fabrizio about 8 years ago

What is the rationale for always adding a (non-anonymous, non-locked) author to the assignable users list? I was caught by surprise on this behavior, since if the author is a member of a non-assignable role I would not expect to find them on the assignable users list, yet they are still included. I want to disable this behavior but want to first make sure I'm not missing an obvious reason why this is being done.

My scenario is that all of our staff can use Redmine to submit tasks/requests to a certain small team we have which is responsible for handling those tasks, but only the team members themselves should be able to be assigned issues. It's confusing to those team members to also see the author on the list of assignable users every time, and they've asked me if I can change that behavior. Seems like a trivial edit to the model but want to make sure I don't inadvertently break something.

Thanks!

Actions
Copy link

Also available in: Atom PDF