Defect #21477

Assign to "Anonymous" doesn't make much sense

Added by Felix Schäfer over 2 years ago. Updated over 1 year ago.

Status:ClosedStart date:
Priority:NormalDue date:
Assignee:Jean-Philippe Lang% Done:

0%

Category:Issues
Target version:3.1.4
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.

21477-dont_add_anonymous_author_to_assignable_users.diff Magnifier (452 Bytes) Felix Schäfer, 2015-12-10 18:17

Associated revisions

Revision 14970
Added by Jean-Philippe Lang over 2 years ago

Don't include anonymous user in assignable users (#21477).

Patch by Felix Schäfer.

Revision 14971
Added by Jean-Philippe Lang over 2 years ago

Adds a test for #21477.

Revision 14972
Added by Jean-Philippe Lang over 2 years ago

Don't include locked user in assignable users (#21477).

History

#2 Updated by Jan from Planio www.plan.io over 2 years ago

  • Target version set to Candidate for next minor release

#3 Updated by Jean-Philippe Lang over 2 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.

#4 Updated by Felix Schäfer over 2 years ago

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

Thanks JPL.

#5 Updated by Jean-Philippe Lang over 2 years ago

  • Target version changed from 3.2.1 to 3.1.4

#6 Updated by Jean-Philippe Lang over 2 years ago

  • Status changed from Resolved to Closed

#7 Updated by Fran Fabrizio over 1 year 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!

Also available in: Atom PDF