This is not a bug. This was done by design because we do not want to change the status of an issue once it was created.

[quote user="SaarCohen"]This is not a bug. This was done by design because we do not want to change the status of an issue once it was created.[/quote]
Still it's an odd thing: if I create an issue, and assign a resource to that issue, the status is also set to 'unassigned'. THis is silly, as the field 'Assigned to' shows the assigned resource, so it IS assigned to someone. Now I have to click a couple of times to get the status switched to assigned.

Also, I can't close an unassigned issue this way, I always first have to set the status to assigned, even when I've selected unassigned as a valid pre-state for closed.

Wrong! You must have something wrong with your status setup.

When you create an issue and assign a resource to it, the status will be assigned!

You can test it on http://gemini.countersoft.com/

[quote user="FransBouma"]Also, I can't close an unassigned issue this way, I always first have to set the status to assigned, even when I've selected unassigned as a valid pre-state for closed.
[/quote]

When you setup unassigned as a valid pre-state for closed, did you update both the unassigned (closed is a post-state) and closed (unassigned is a pre-state) status? I have made the mistake of not updating both status relationships before.

[quote user="MarkWing"]

Wrong! You must have something wrong with your status setup.

When you create an issue and assign a resource to it, the status will be assigned!

You can test it on http://gemini.countersoft.com/

[/quote]
Please don't come up with 'Wrong!', I experience this behavior every darn day here so I'm not lying about this. If it's something with the status setup, great, but WHAT is then wrong with the status setup? I can't imagine what the status setup has to do with it. If I assign a resource to an issue I'm CREATING, I expect the status to become 'assigned'.

Though I think I know what's wrong: the Assigned status isn't having its 'Assigned status' checkbox checked. I haven't touched that, so it might be that that's something not initially set correctly.

[quote user="bygate"]

[quote user="FransBouma"]Also, I can't close an unassigned issue this way, I always first have to set the status to assigned, even when I've selected unassigned as a valid pre-state for closed.
[/quote]

When you setup unassigned as a valid pre-state for closed, did you update both the unassigned (closed is a post-state) and closed (unassigned is a pre-state) status? I have made the mistake of not updating both status relationships before.[/quote]

After reading your post I re-checked the states again, and then I saw that Closed wasn't a post-state for unassigned! After I made the changes there, it worked. :)