If '#' appears in the commit message, what follows it is interpreted as a smart commit transition. E.g. messages

• FE-123: remove reduntant MyClass#someMethod field
• JIRATEST-1 http://crucible.domain.com/cru/CR-TEST-1#c1234

try to execute someMethod/c transitions respectively. Usually that fails*, because such transitions do not exist, but we might get an unwanted transition, e.g. by committing "FE-123: Remove redundant MyClass#close method".

* Failed transition triggers an e-mail to user:

Error processing FE-123 #someMethod field
FishEye was unable to execute the transition "someMethod" on the issue FE-123 due to the following unexpected error: No transitions for issue FE-123 (In Progress) matched the command 'someMethod'. Valid transitions are: QA, Stop Progress, Code Review, Close Issue

Simple solution would be to only interpret the '#' if preceded by whitespace or new line.