Redmine

I also disagree - there is no magic quality about 'assigned' that says it will be:

1. Always present
2. The correct status to pick in each situation.

Brad Mace wrote:

I think this could be done relatively simply. When configuring issue statuses, there are already checkboxes for 'Issue Closed' and 'Default Value'. All that would be needed is a 'Set when Assigned' option.

It wouldn't be that simple. What if two Issue Statuses where given "Set when Assigned"? What about if User A assigns the issue but they don't have permission to change the status (via workflow)?

I was assuming you'd only be able to pick one status to be 'Set when assigned'. At the moment I can't think of any scenario where it would make sense to want more than one.

As for permissions, I'm thinking that if the person has permission to assign issues, the automatic status change should be allowed, even if they wouldn't have permission to choose the 'Assigned' status manually. It seems safe to assume that if an administrator chooses a status to be set when assigned, they'd want that to be done anytime an issue is assigned. It may even be preferable not to allow setting the assigned status manually, because someone could potentially set the status to assigned while not actually assigning it to anyone.

Anyway, just wanted to offer my suggestion on how such a thing might be done since implementation hadn't been discussed at all. As a fellow programmer I know things may be a lot more complicated than they initially appear. If there won't be any way to have the 'Assigned' status set automatically, then I'd suggest that 'Assigned' be removed from the default configuration. Having to set it manually makes it too easy for things to get into an inconsistent state. Perhaps 'New' and 'Assigned' should be replaced by 'Open' in that case?