I'd flag this as a bad idea: say the "assigned to" field is filled according to "category" or anything else, and that assignee is head of a department in charge of assigning it to someone in said department, automatically setting the "status" field to "assigned" would then be false information, as said person is not in charge of the actual implementation but of assigning the ticket to someone.
--------------------------------------------------------------------------------
I think status should definitely be set to Assigned automatically. I'm not sure why it hasn't been like that all along. It's kind of annoying to have to remember to set two things when you want to assign the issue to somebody.

Re: Felix's case, I wonder if that's really all that common. Besides, if you assign it to somebody who will assign it to someone else, technically, the issue's been looked at and assigned to _someone_, right? It's just that the work hasn't begun yet (but you should really have another status that you set manually if you want to track that information). Even so, I guess there should probably be a configuration option in the backend to disable auto-assigning (it could be enabled by default).
--------------------------------------------------------------------------------
I have to agree with the original issue and Elliot Winkler.

To me, and the other people using the software here. The "Assigned to" field translates to "If you need something done on this issue then talk to this person"

To use Felix's example: If an issue is assigned to a manager (via the category field) who hasn't assigned it to a developer then I need to bug the manager to do his thing so that the bug can be progressed.

To us a "New" issue is an issue that no one has looked at yet and can't be automatically assigned (via categories for example) so requires someone to actively intervene.

--------------------------------------------------------------------------------
Elliot Winkler wrote:
> I think status should definitely be set to Assigned automatically. I'm not sure why it hasn't been like that all along. It's kind of annoying to have to remember to set two things when you want to assign the issue to somebody.
> [...]

The status "Assigned" won't be available out of the box in Redmine version#6. See issue #3605.
--------------------------------------------------------------------------------
Can we have a more flexible solution then (more work though).

In the issue statuses we currently have a default "start" status. Would it be possible to set a default status that should be selected when the assigned_to field is _first_ populated.

Have some JS on the issues page that will set the status accordingly when the assigned_to field is populated and the issue is currently on the default start status. A very crude state-machine if you will.
--------------------------------------------------------------------------------
Mischa is correct, #3605 renamed the default "Assigned" status to "In Progress".

I've reword the subject to describe setting a status when an issue is first assigned.
--------------------------------------------------------------------------------

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

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

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

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

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

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

relates,New,640,When choosing assignee, automatically switch status to Assigned
relates,New,2128,Problems when 'Assigned To' field doesn't match 'Assigned' issue tracker
duplicates,Closed,349,New product, assign task to someone should set status to "Assigned"
duplicates,Closed,7124,Assigning an Assignee should change the issue status