Fixing issues in commit messages can break the workflow
I have a redmine instances with trackers with orthogonal states (for example, task have a state "done" instead of "fixed" for bugs). In the workflow, a task can never be in "fixed" state and for that reason, can't go to any other state from "fixed" state..
On the other hand, I have the option "Referencing and fixing issues in commit messages" activated but I can only specify one "Applied status" (which I have in fixed).
The problem is, if a commit message closes a task, the task is set to be in "fixed" state, but (apart from being wrong) it can't be changed (unless I make the workflow less restrictive, which I rather not).
So, I think it would be great if one can specify a "default" closed state for a tracker, and have a option in "Applied status" that says "Default closed state" or something like that, so when a commit closes an issue, the correct state can be set.
It would be great too if one can specify how to close the issue in the commit message (something like "closes #1234 (fixed)".
Using Redmine 0.7.2.1557 (MySQL).